Skip to content

build.cmd fails to pick the right MSVC toolset on 1es-windows-2022-open #100046

Closed
@antonfirsov

Description

@antonfirsov

The following simple pipeline fails to build the runtime on 1es-windows-2022-open outside of docker:

trigger: none

pr:
  branches:
    include:
    - "*"

variables:
   - template: ../variables.yml

extends:
  template:  /eng/pipelines/common/templates/pipeline-with-resources.yml
  parameters:
    stages:
    - stage: Build
      jobs:
      - job: windows
        displayName: Test
        timeoutInMinutes: 150
        pool:
          name: $(DncEngPublicBuildPool)
          demands: ImageOverride -equals 1es-windows-2022-open

        steps:
        - checkout: self
          clean: true
          fetchDepth: 5
          lfs: false

        - powershell: |
            & "$(Build.SourcesDirectory)/build.cmd" clr+libs -ci -rc Release -c Release
          name: buildRuntime
          displayName: Build CLR and Libraries

For the repro see this build from #100038.

The build fails to pick the right MSVC toolset even though it's present on the machine (see #95750 (comment)), and as a result will run into #94723. This is the root cause of #95750 which is blocking HTTP and SSL stress runs on CI.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions