Skip to content
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

Closed
v-ainigao opened this issue May 14, 2024 · 9 comments
Labels
Area-DotNet Test untriaged Request triage from a team member

Comments

@v-ainigao
Copy link

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

using Microsoft.VisualStudio.TestTools.UnitTesting;
namespace TestProject3
{
    [TestClass]
    public class UnitTest1
    {
        [TestMethod]
        public void TestMethod1()
        {
            Assert.AreEqual(11, 11);
        }
        [TestMethod]
        public void TestMethod2()
        {
            Assert.AreEqual(1, 11);
        }
        [TestMethod]
        public void TestMethod3()
        {
            Assert.Inconclusive();
        }
    }
}

4.run dotnet build
5.run dotnet test

Expected Result:
The generated log should default to arm64.

Actual Result:
The generated log is x64.
1
note:
In dotnet test --help, I did not see the prompt that the default generated log is x64.
image
image
image

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-DotNet Test untriaged Request triage from a team member labels May 14, 2024
@v-xiaofchen
Copy link

This issue also repro on Mac-arm64 OS.
image

@v-ainigao
Copy link
Author

@MarcoRossignoli This issue is still repro in .net9preview4, I want to know the reason for the close and can we ignore it?
image

@MarcoRossignoli
Copy link
Member

MarcoRossignoli commented May 20, 2024

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

@v-ainigao
Copy link
Author

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.

@MarcoRossignoli
Copy link
Member

Most likely will be fixed in the next patch version of MSTest, @Evangelink can you confirm or give some ETA?

@Evangelink
Copy link
Member

I will be releasing a fix tomorrow or on Wednesday.

@v-ainigao
Copy link
Author

This issue also repro's in .net9preview5.Is it still under fixed?
image

@Evangelink
Copy link
Member

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.

@v-ainigao
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-DotNet Test untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

4 participants