-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Find VC.Tools.ARM64 on arm64 machine #3075
base: main
Are you sure you want to change the base?
Conversation
Hey @saschanaz thanks for this PR! macOS seems to be failing with these changes. Can you please investigate it and see why that is happening? Thanks in advance. P.S. I remember this PR we had some time ago. Not sure it is connected to this but it also had some ARM64 specifics. |
That's exactly because what I said earlier:
|
The last test failure seems irrelevant to my patch and more random? |
Three attempts failed, I wonder it passes on the main branch. |
I ran those attempts. Just minutes ago, I thought to give it another chance before replying to this, and it has passed now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change looks good. Would still like to see someone else take a look before landing.
Checklist
npm install && npm run lint && npm test
passesDescription of change
Fixes #3074
VC.Tools.ARM64
gives the native ARM64 binaries for MSVC, and this patch detects that on arm64 Node.js.Help needed for a test. A fixture that only have ARM64 binary may work but such test would only pass on arm64 test runner machine. And not sure how to generate such fixture. (Just remove x86.x64 from the existing 2022 fixture?)
Also this patch makes some existing tests fail on ARM64 machine because not all fixtures have ARM64 MSVC (as older VS just didn't have it). Help needed for that too. Skip them somehow?Now it falls back to x86 if arm64 tool doesn't exist.