Uh oh!
There was an error while loading. Please reload this page.
test: keep WPT backend checks alive - #65320
Conversation
Signed-off-by: Filip Skokan <panva.ip@gmail.com>
This comment was marked as outdated.
This comment was marked as outdated.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## main #65320 +/- ##
==========================================
- Coverage 90.12% 90.11% -0.01%
==========================================
Files 752 752 Lines 251569 251569 Branches 47264 47273 +9 ==========================================
- Hits 226724 226712 -12 - Misses 16188 16213 +25 + Partials 8657 8644 -13 🚀 New features to boost your workflow:
|
aduh95
left a comment
There was a problem hiding this comment.
This is not ideal, feeling the need to add a setTimeout is quite smelly, but is certainly OK as a temporary solution
This comment was marked as outdated.
This comment was marked as outdated.
Yeah the test runner's natural timeout might as well be used as a stop gap instead. I'll revisit this if need be. |
nodejs-github-bot
commented
Aug 16, 2026
| ); | ||
| try { | ||
| await handle.finished; | ||
| } finally { |
There was a problem hiding this comment.
[nit]: we should add a catch block here as well
Uh oh!
There was an error while loading. Please reload this page.
nodejs-github-bot
commented
Aug 18, 2026
Landed in 1c9baec |
Signed-off-by: Filip Skokan <panva.ip@gmail.com> PR-URL: #65320 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Aviv Keller <me@aviv.sh> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Deflakes
parallel/test-common-wpt-backends.