-
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
Skip the long path tests when not on Windows #4116
Conversation
@@ -1,4 +1,7 @@ | |||
'use strict'; | |||
|
|||
if (process.platform !== 'win32') process.exit(); |
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.
Can you use the TAP-compatible approach we use e.g. here?
(I forgot about common.isWindows
, it's fairly new.)
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.
I changed the test skipping in 5502b9b - is that what you mean?
LGTM, thanks. Can you squash and write a commit log in the style that CONTRIBUTING.md wants? |
@bnoordhuis I rebased it on fresh master, squashed into e07b145 with new message and force pushed here. I can't access the CI link ("rsp is missing the Overall/Read permission") so I don't know if it tests the forced update automatically or not. Thanks for your help. |
LGTM |
As @rsp updated, new CI : https://ci.nodejs.org/job/node-test-pull-request/932/ |
LGTM if new CI is happy :) |
If not running on Windows it skips the long path tests in: * test-fs-long-path.js * test-require-long-path.js Fixes: #2255 PR-URL: #4116 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
Thanks, landed in 19e06d7. |
If not running on Windows it skips the long path tests in: * test-fs-long-path.js * test-require-long-path.js Fixes: #2255 PR-URL: #4116 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
@jasnell @JungMinu @bnoordhuis @rvagg Thanks. My pleasure. I think the |
If not running on Windows it skips the long path tests in: * test-fs-long-path.js * test-require-long-path.js Fixes: #2255 PR-URL: #4116 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
If not running on Windows it skips the long path tests in: * test-fs-long-path.js * test-require-long-path.js Fixes: #2255 PR-URL: #4116 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
If not running on Windows it skips the long path tests in: * test-fs-long-path.js * test-require-long-path.js Fixes: nodejs#2255 PR-URL: nodejs#4116 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
This is another attempt to fix the tests failing on Ubuntu (see issue #2255)
This time by skipping the tests when not on Windows (as advised by @bnoordhuis)
Other PRs that solve the same issue:
See also comments to PRs #3925 and #3929 for more context.