GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||
GeezerVison is showing github.com — test: ignore helper files in WPTs by panva · Pull Request #48079 · nodejs/node Conversation
Member
Because daily WPT report started timing out on these helper files. These are not test entrypoints so we're not losing any coverage.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Collaborator
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
aduh95
reviewed
Uh oh!
There was an error while loading. Please reload this page.
anonrig
approved these changes
Member
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
KhafraDev
approved these changes
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Although there's no harm in skipping these files, I don't understand why they would time out. Is it a deeper problem with the WPT runner?
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
The way it selects files that contain tests is definitely one. Combined with the recent change to register a timeout to keep the event loop spinning being another, I wanted to avoid that but the wpt maintainers weren't keen to acknowledging our event loop and called my patch to a particular test a bug hiding solution instead. We can go with this workaround for now until I get the time to pull in the native WPT python tool scripts that build the manifest of files to run. That should avoid any future test file selection problems. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Landed in 6439f68 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #48079 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
PR-URL: #48079 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
PR-URL: nodejs#48079 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
PR-URL: nodejs#48079 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
PR-URL: nodejs#48079 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.