-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Investigate flaky test test-fs-symlink #3311
Comments
joaocgreis
added
build
Issues and PRs related to build files or the CI.
test
Issues and PRs related to the tests.
labels
Oct 10, 2015
mscdex
added
fs
Issues and PRs related to the fs subsystem / file system.
windows
Issues and PRs related to the Windows platform.
and removed
build
Issues and PRs related to build files or the CI.
labels
Oct 10, 2015
So this isn't flaky but it just doesn't work on windows 10, right? |
That's likely to be it, yes. I didn't get a chance to look at it yet, just opened the issue since we have Windows 10 on CI now and it's failing there. |
I believe #3418 will fix this. |
Trott
added a commit
to Trott/io.js
that referenced
this issue
Oct 18, 2015
If the symlink portion of the test was being skipped due to a combination of OS support and user privileges, then an assertion would always fail. This fixes that problem, improves assertion error reporting and renames the test to make it clear that it is a test for links and not just symlinks. Fixes: nodejs#3311
Trott
added a commit
that referenced
this issue
Oct 21, 2015
If the symlink portion of the test was being skipped due to a combination of OS support and user privileges, then an assertion would always fail. This fixes that problem, improves assertion error reporting and splits the test to make it clear that it is a test for links and symlinks. Fixes: #3311 PR-URL: #3418 Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Trott
added a commit
that referenced
this issue
Oct 26, 2015
If the symlink portion of the test was being skipped due to a combination of OS support and user privileges, then an assertion would always fail. This fixes that problem, improves assertion error reporting and splits the test to make it clear that it is a test for links and symlinks. Fixes: #3311 PR-URL: #3418 Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Trott
added a commit
that referenced
this issue
Oct 29, 2015
If the symlink portion of the test was being skipped due to a combination of OS support and user privileges, then an assertion would always fail. This fixes that problem, improves assertion error reporting and splits the test to make it clear that it is a test for links and symlinks. Fixes: #3311 PR-URL: #3418 Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
This was referenced Feb 20, 2022
This was referenced Sep 29, 2022
This was referenced Oct 5, 2022
This was referenced Oct 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Examples of failures:
win10
Failed every time I tried it in Windows 10.
The text was updated successfully, but these errors were encountered: