New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.WindowsDesktop.App missing on 'windows-2022' #8859
Comments
Hey @PeterBenko, thank you for reporting. We will investigate it. |
We are having the same issue with our build pipelines both when we try UseDotnet in a separate installation path
|
can you please run |
The issue might be unrelated to the images, since we se the same issue both on our self-hosted agents (azure scale-sets using server 2022 image) and when running this image. The issue is the same regardless of which version of dotnet we try to add (tested 6,7 and 8) Before:
After:
Running the images we get:
After:
|
looks like there's something wrong with |
DotNet SDKs installed by image are located at somehow after using what was installed and why it does not work as expected, I'd say is "somewhere on DotNetCoreCLI@2 side" |
I might add that running build works just fine, the issue only arises when running tests targeting x86.
Compared to when running using the hosted images:
|
@fredrikloch we do not provide any x86 dotnet runtimes/sdks in the image (and never did), whatever is installed for x86 being installed in your pipeline runtime, I'd say there is a need to report this problem to the https://github.com/microsoft/azure-pipelines-tasks repository |
@mikhailkoliada I will check there, however the last run output suggests that there is something installed for x86 in this image.
Is from a run where I've used no separate "UseDotnet" step in the setup. |
can you please collect msbuild binlog from you build ? it should produce |
I've received a second hand confirmation of this from someone working with a MS Support engineer |
@PeterBenko Is there a public bug report that we can follow? |
@ilia-shipitsin here is a build log of the failing steps for us:
And the following output for dotnet --info:
It also seems to be unrelated to issues in DotNetCoreCLI@2 since there is no change in version of that task between the runs before and after this issue both use version 2.221.0 |
I'm also seeing this issue - even when attempting to ensure that .net 6 is installed, the installation fails, then the test fails:
|
Closing as non-image connected:
|
Description
With the new image of windows-2022,
DotNetCoreCLI@2
test
runs fail for a x86 project.Platforms affected
Runner images affected
Image version and build link
Image: windows-2022
Version: 20231115.2.0
Included Software: https://github.com/actions/runner-images/blob/win22/20231115.2/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20231115.2
Is it regression?
YES - same pipeline passed with
windows-2022
20231029.1.0
Expected behavior
DotNetCoreCLI@2
test
runs should be possible for x86 based projects.Actual behavior
The test run fails due to missing
.NET 6
x86
Microsoft.WindowsDesktop.App
With further investigation by logging
dotnet --info
in the pipeline it becomes evident that x86 toolkit on 20231115.2.0 doesn't match the x64 one:dotnet --info:
C:"Program Files (x86)"\dotnet\dotnet.exe --info
Repro steps
Execute unit test for a project targetting
net6.0-windows
framework andx86
platform withDotNetCoreCLI@2
onwindows-2022
20231115.2.0
The text was updated successfully, but these errors were encountered: