process-reports: taint subtest timeouts by suspicion
#85
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, if one is running a WebGPU CTS test such that there's not a deterministic place it will time out (like the tests with thousands of tiny subtest cases that simply don't fit in the time budget `wptrunner` gives them), it can take dozens to hundreds of runs to empirically observe every single potential point of concretely timing out. This is a problem when the goal is to converge expected outcomes in as few runs as possible! Resolve this as follows: If over the course of processing we encounter any reconciled subtest outcomes that contain a `TIMEOUT` or `NOTRUN` value, ensure _both_ `TIMEOUT` and `NOTRUN` are present in the reconciled subtest outcomes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, if one is running a WebGPU CTS test such that there's not
a deterministic place it will time out (like the tests with thousands of
tiny subtest cases that simply don't fit in the time budget
wptrunnergives them), it can take dozens to hundreds of runs to empirically
observe every single potential point of concretely timing out. This is
a problem when the goal is to converge expected outcomes in as few runs
as possible!
Resolve this as follows: If over the course of processing we encounter
any reconciled subtest outcomes that contain a
TIMEOUTorNOTRUNvalue, ensure both
TIMEOUTandNOTRUNare present in thereconciled subtest outcomes.