-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[NETSDKE2E][ARM64]After installing net9preview4SDK on the arm64OS, create the MStest project and run dotnet test. The generated log is x64. #40857
Comments
@MarcoRossignoli This issue is still repro in .net9preview4, I want to know the reason for the close and can we ignore it? |
Sorry for the confusion this issue is not related to the SDK self but to the testing platform where the core sources resides here https://github.com/microsoft/testfx/tree/main/src/Platform/Microsoft.Testing.Platform The issue is inside the package https://www.nuget.org/packages/Microsoft.Testing.Platform.MSBuild that's closed source. We fixed it and will be soon shipped. Also it's a UX/filename issue the application will run with the correct architecture. cc: @Evangelink @nohwnd |
Okay, thank you for your explanation, I'll keep checking until the right platform shows up. |
Most likely will be fixed in the next patch version of MSTest, @Evangelink can you confirm or give some ETA? |
I will be releasing a fix tomorrow or on Wednesday. |
Sorry @v-ainigao, we got a couple of other bug fixes to include. I have just done the release and will update the test-template now. |
That's all right, I will keep tracking. thank you. |
Build:
9.0.100-preview.4.24260.3
Repro steps:
1.Install .net9 preview4 SDK on arm64.
2.Create a MStest project in CLI.
dotnet new mstest
3.Add test code in UnitTest1.cs
notepad UnitTest1.cs
4.run
dotnet build
5.run
dotnet test
Expected Result:
The generated log should default to arm64.
Actual Result:
The generated log is x64.
note:
In
dotnet test --help
, I did not see the prompt that the default generated log is x64.The text was updated successfully, but these errors were encountered: