Bug 252268
| Summary: | WPT testharness subtests should be unordered | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sam Sneddon [:gsnedders] <gsnedders> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | sihui_liu, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=299830 https://bugs.webkit.org/show_bug.cgi?id=315857 |
||
| Bug Depends on: | |||
| Bug Blocks: | 252269 | ||
Sam Sneddon [:gsnedders]
Per the WPT testharness API contract, only the mapping from subtest name to subtest status is meaningful, not the ordering of the subtests.
Note that this is one place where Chromium also doesn't match, except in the simplest all-PASS cases.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/105469778>
Sam Sneddon [:gsnedders]
https://github.com/WebKit/WebKit/commit/7dc7c1f5a8abc337fb5cc365f03161e2c536480e from bug 315857 added a bunch of gnarly code to workaround the fact we don't do this, by effectively doing this when site isolation is enabled.
We really should just fix this in all cases, despite the historic opposition to non-deterministic subtest ordering from some WebKit contributors, because operationally we can't really keep on making tests slower to try and make the ordering deterministic, especially when the upstream consensus is clearly in favour of quicker running tests.