[testharness.js] Preserve harness error message #20168
Merged
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.
This change does not modify tests because it only effects the harness status string, and we do not validate that.
I checked the "raw" wpt.fyi results for gh-20036. There were 10 occurrences of the generic harness error message in Chrome's data:
Firefox had a significantly greater number:
Following the application of this patch, both browsers report just one test--a legitimate and previously-unreported testing error:
That test was merged after gh-20036, so we shouldn't lose sleep about any lack of care. It was most likely submitted from a branch that didn't include the
single_test
enforcement. In any event, I've opened gh-20167 to correct it.Reviewing this patch's effect on results more generally, it doesn't appear to have any unintended side effects:
Although many of the discrepancies are due to pre-existing instabilities, I haven't yet reviewed all of them. I'm opening this pull request now because this problem is blocking gh-19993, so others can verify in my place if they want to move forward before I return tomorrow (EST).