-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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: make test-fs-watchfile reliable #13385
Conversation
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.
LGTM
Stress tests indicate this doesn't fix the flakiness on AIX. I'm starting to wonder if sometimes AIX hands us watchers that will simply never fire. The |
Watch facility on folders are not fool-proof in AIX, and we have skipped those tests which do that. I guess the new changes in #13111 made that change, it's original intent was to make sure the filename argument appears in the callback, when it fires - so I requested to include AIX as well, as the filename argument is availabe in that platform. But then the change introduced folder watch and hence the flaky result. Proposals - one of:
|
Thanks, @gireeshpunathil! I've moved the test back to parallel and updated it to skip the directory watch test on AIX. |
(Whoops, will need to update the commit message when landing.) |
Omitting AIX from `fs.watch()` portion of this test. It works on AIX, but not reliably. Fixes: nodejs#13377
@refack I've change the error throwing stuff back to the way it was. I don't feel strongly about it and I have mixed feelings about doing small-but-unrelated refactors with more meaningful changes anyway. So happy to put it back the way you like. It also gave me an opportunity to fix the commit message! CI again: https://ci.nodejs.org/job/node-test-pull-request/8442/ |
Test failure on OS X is unrelated (and is something that will be fixed coincidentally by a NodeTodo task I just gave to someone yesterday). Thoughts on merging this now rather than waiting the 72 hours on the grounds that it's trivial and fixes a CI issue? |
👍 |
Landed in 98aa25c |
Omitting AIX from `fs.watch()` portion of this test. It works on AIX, but not reliably. PR-URL: #13385 Fixes: #13377 Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Omitting AIX from `fs.watch()` portion of this test. It works on AIX, but not reliably. PR-URL: #13385 Fixes: #13377 Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#13411 Refs: nodejs#13385 Refs: nodejs#13248 Refs: nodejs#13377 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
Fixes: #13377
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test fs