test: split test-runner-run-watch.mjs

[joyeecheung]

This test contains too many independent test cases and as a result, marking it as flaky on all major platforms means actual regressions could be covered up, and it's constantly making the CI orange and requires extra resuming on the flaked platforms which is still not great. Also, it can increase the flakiness when the tests share the same files being watched due to file system events coalescing. Split it into individual files so that the actual flake can be identified out of the monolith and reduce flakiness.

Refs: #54534

[nodejs-github-bot]

Review requested:

• @nodejs/test_runner

[mcollina]

lgtm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.45%. Comparing base (8e5c80d) to head (27796e6).
⚠️ Report is 33 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #60653      +/-   ##
==========================================
- Coverage   88.54%   88.45%   -0.09%     
==========================================
  Files         704      703       -1     
  Lines      208103   208058      -45     
  Branches    40089    40001      -88     
==========================================
- Hits       184256   184031     -225     
- Misses      15876    16029     +153     
- Partials     7971     7998      +27     

see 62 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/70115/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/70124/

[joyeecheung]

I copied the original logic in

node/test/parallel/test-runner-run-watch.mjs

Lines 80 to 83 in 9524908

	const interval = setInterval(() => writeFileSync(path, content), common.platformTimeout(1000));
	await ran2.promise;
	runs.push(currentRun);
	clearInterval(interval);

here because I want to keep this PR strictly a split, and not change logic for now, so this is not reusing that performFileOperation() helper; test-run-watch-dependency-repeatedly.mjs flaked in https://ci.nodejs.org/job/node-test-pull-request/70115/ and I think the culprit might be in this logic - the interval fires too fast and before the test finishes, the write fires, then the watched process get killed with SIGTERM to run again. I think the follow up to deflake it might be to just do what's in the branch below and not do the interval.

(I am somewhat puzzled why it's using an interval in the original logic, I think update + timeout like the branch below which was split from the --watch test should suffice; repeated updates could trigger additional events that kill the process being watched unexpectedly @mcollina )

[nodejs-github-bot]

Landed in ea1a240