-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
test,win: skip addons/load-long-path on WOW64 #6675
Conversation
What kind of system is |
LGTM although it's more commonly spelled as "WoW64", I think? @Fishrock123 Windows 32 bits on a Windows 64 bits host. |
I went with the official spelling by Microsoft, I can change it if you feel strongly about it. https://msdn.microsoft.com/en-us/library/windows/desktop/aa384274(v=vs.85).aspx
|
No strong feelings. |
I'll wait for #6697 to land and adopt the new skip syntax. |
@orangemocha #6697 has landed, you should be able to use the new syntax here. |
f1d5293
to
ec9f8f4
Compare
Updated, thanks! |
LGTM |
I am confident that the CI failures on ARM are unrelated to this change. /cc @nodejs/testing https://ci.nodejs.org/job/node-test-binary-arm/2285/RUN_SUBSET=6,label=pi1-raspbian-wheezy/ Landing shortly. |
ec9f8f4
to
6e2ae8a
Compare
This test fails on WOW64 because of a bug in the OS, and there is no acceptable workaround. Ref: nodejs#3667 PR-URL: nodejs#6675 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: cjihrig - Colin Ihrig <cjihrig@gmail.com>
@orangemocha could this be backported? Still seeing this on 4.4.7. |
This test fails on WOW64 because of a bug in the OS, and there is no acceptable workaround. Ref: nodejs#3667 PR-URL: nodejs#6675 Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: cjihrig - Colin Ihrig <cjihrig@gmail.com>
Checklist
Affected core subsystem(s)
test,win
Description of change
This test fails on WOW64 because of a bug in the OS, and there is
no acceptable wokaround.
Ref: #3667