Conversation
|
CC @anonrig |
|
CC @nodejs/fs |
b5f62bb to
5dbf508
Compare
|
@anonrig do you have any idea why this might crash the CI? |
anonrig
left a comment
There was a problem hiding this comment.
I mostly think that due to the async nature of fs.watch is causing the errors to fail. Please add a timeout after listening
5dbf508 to
75f4a97
Compare
|
@anonrig I have implemented your suggestions, but it is not just a test failure - the build seems to crash |
75f4a97 to
1699f00
Compare
|
I think you need to skip the tests for only AIX and IBMi. |
I am just trying to figure out why the build is crashing |
c0fefbe to
fa63c9b
Compare
170cade to
2d6f225
Compare
2d6f225 to
7b63ee7
Compare
|
will handle this after #45214 since they conflict as well |
6812665 to
dc77925
Compare
anonrig
left a comment
There was a problem hiding this comment.
I believe that the issue with lib/internal/fs/recursive_watch.js should be committed separately in a different pull request. Other than that, I've added some comments. Thank you for your contribution!
dc77925 to
93532f3
Compare
93532f3 to
03e801d
Compare
follow up for #45098
adapting recursive file watching into watch mode