Closed hakenmt closed 2 years ago
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries See info in area-owners.md if you want to be subscribed.
Author: | hakenmt |
---|---|
Assignees: | - |
Labels: | `area-Infrastructure-libraries` |
Milestone: | - |
Likely the same as https://github.com/microsoft/vstest/pull/1927. Sounds like VSTest doesn't support arm64 today?
cc @nohwnd @MarcoRossignoli
Test platform today supports ARM64.
ARM64 was been added here https://github.com/microsoft/vstest/pull/3003/files#diff-7ab61afc88751e74038b5ef7068376b71882aad25297172096230dc63f3131e0 on 5 August 2021.
My suspect is that you're running tests with the netcoreapp3.1 SDK that's too old.
Can you run dotnet --info
?
Yes, this build is using netcoreapp3.1. But EOS for that isn't until December. Shouldn't it have parity for this?
Back porting to old version wasn't planned and we didn't have request for that since now for what I know. We can move this issue to the vstest repo and wait to see if there're others request for that.
Yes, I think this issue should be moved into the vstest repository as it isn't actionable on our side.
@ViktorHofer you can close this one thanks
@MarcoRossignoli can you please link to the new one opened?
Description
I'm running the following command on my test project.
This results in an error.
Invalid platform type:arm64. Valid platform types are x86, x64 and Arm.
When
arm
is specified forPlatformTarget
, the command works, but the platform and processor parameters are not passed to the build of the main project. In the project, I'm using conditions for the TargetFramework like this:I can tell the parameters aren't being passed because the build tries to target
net6.0
when it should be targetingnetcoreapp3.1
. I would expect the build of both projects to use the provided parameters.Configuration
This is being run in an AWS CodeBuild environment on an Amazon Linux 2 ARM64 container.
Regression?
Not sure if this problem exists elsewhere.
Other information