Skip to content

test: make fs watch test more stable

The test currently uses a timeout to deal with a watch event for the directory being created.

This is flaky e.g. https://ci.nodejs.org/job/node-test-binary-windows-js-suites/RUN_SUBSET=2,nodes=win10-COMPILED_BY-vs2019/lastCompletedBuild/testReport/(root)/test/pummel_test_fs_watch_non_recursive_/

Instead this changes the common.mustNotCall to allow calls with testdirname so we do not depend on timing as much.

Merge request reports

Loading