| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
cc @nodejs/timers |
Sorry, something went wrong.
Sorry, something went wrong.
|
I understand the motivation, but is there an alternative, such as adding an option to run some WPTs sequentially or so? |
Sorry, something went wrong.
Not when the other WPT suites execute in parallel. The problem appears to be in used up resources, and with webcrypto hogging those up... |
Sorry, something went wrong.
|
ping @nodejs/timers |
Sorry, something went wrong.
If we're already parallelizing WPT suites in the WPT runner, shouldn't we run test/wpt sequentially? |
Sorry, something went wrong.
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. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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