test: port flaky wpt/html/webappapis/timers tests to test/sequential

[panva]

wpt/test-timers has been unreliable since we've re-enabled parallel execution in WPTs. This PR removes the html/webappapis/timers WPTs and ports the tests to test/sequential instead.

e.g.
nodejs/reliability#548

[panva]

cc @nodejs/timers

[nodejs-github-bot]

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

[tniessen]

I understand the motivation, but is there an alternative, such as adding an option to run some WPTs sequentially or so?

[panva]

I understand the motivation, but is there an alternative, such as adding an option to run some WPTs sequentially or so?

Not when the other WPT suites execute in parallel. The problem appears to be in used up resources, and with webcrypto hogging those up...

[panva]

ping @nodejs/timers

[targos]

Not when the other WPT suites execute in parallel. The problem appears to be in used up resources, and with webcrypto hogging those up...

If we're already parallelizing WPT suites in the WPT runner, shouldn't we run test/wpt sequentially?

[panva]

Not when the other WPT suites execute in parallel. The problem appears to be in used up resources, and with webcrypto hogging those up...

If we're already parallelizing WPT suites in the WPT runner, shouldn't we run test/wpt sequentially?

I'm just looking at nodejs/reliability and wpt/test-webcrypto also occasionally crashes. So i'm going to open a PR reverting the python side of things to sequential and also introducing maximum parallelism option in the WPTRunner.

[panva]

Closing in favour of #47834