| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Let the check for the error code suffice and don't check for a particular string in the message. Fixes: nodejs#33759
Unfortunately, the test is sensitive to resource constraints and is unreliable on macOS in CI when in parallel. Fixes: nodejs#34727
|
Stress test that will hopefully show the issue on master: https://ci.nodejs.org/job/node-stress-single-test/165/ |
Sorry, something went wrong.
|
Do we know why the test is sensitive to resource constraints? |
Sorry, something went wrong.
I'm guessing because it opens a lot of files (128). |
Sorry, something went wrong.
Sorry, something went wrong.
An alternative we could experiment with is halving all the hard-coded numbers. |
Sorry, something went wrong.
|
IMO the sensitivity to resource constraints is by design in the test, and it actually helped (and helps) to detect unforeseen control paths that are not covered in code and test, so is best placed to run in /parallel. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
(Includes the change in #34727 to avoid subsequent merge conflict. This supplants it.)
Unfortunately, the test is sensitive to resource constraints and is
unreliable on macOS in CI when in parallel.
Fixes: #34727
Checklist