Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split html/.../query-encoding/ tests #21881

Merged
merged 1 commit into from
Feb 25, 2020
Merged

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Feb 19, 2020

These tests cover 5 encodings (UTF-8, UTF-16LE/BE, Windows-1251/1252)
and exercise many features (HTML, CSS, SVG, Workers, ...). They're
currently all skipped in Chrome (and other browser CI systems), since
something in that huge matrix fails or times out for everyone.

#4934 suggests
splitting these into separate files. As a stopgap, split them out
using the WPT "variant" mechanism and provide expected failure files
for subsets, which should make fixing the tests and/or browsers more
actionable, and let us catch new regressions.

Bug: 930297
Change-Id: I4813281f547216b2b5f377118a58a419f62cfbc7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063808
Commit-Queue: Philip Jägenstedt <[email protected]>
Reviewed-by: Philip Jägenstedt <[email protected]>
Cr-Commit-Position: refs/heads/master@{#743019}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@foolip
Copy link
Member

foolip commented Feb 20, 2020

wpt-firefox-nightly-stability is failing like this:

Unstable results

Test Subtest Results Messages
/html/infrastructure/urls/resolving-urls/query-encoding/utf-16be.html?include=workers OK: 9/10, TIMEOUT: 1/10
/html/infrastructure/urls/resolving-urls/query-encoding/utf-16be.html?include=workers SharedWorker constructor PASS: 9/10, TIMEOUT: 1/10 Test timed out
/html/infrastructure/urls/resolving-urls/query-encoding/utf-16le.html?include=workers OK: 8/10, TIMEOUT: 2/10
/html/infrastructure/urls/resolving-urls/query-encoding/utf-16le.html?include=workers SharedWorker constructor PASS: 8/10, TIMEOUT: 2/10 Test timed out
/html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html?include=workers OK: 7/10, TIMEOUT: 3/10
/html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html?include=workers SharedWorker constructor PASS: 7/10, TIMEOUT: 3/10 Test timed out
/html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html?include=workers OK: 9/10, TIMEOUT: 1/10
/html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html?include=workers SharedWorker constructor PASS: 9/10, TIMEOUT: 1/10 Test timed out

That ought to be a pre-existing problem, so I'll admin merge this when https://chromium-review.googlesource.com/2063808 has landed.

These tests cover 5 encodings (UTF-8, UTF-16LE/BE, Windows-1251/1252)
and exercise many features (HTML, CSS, SVG, Workers, ...). They're
currently all skipped in Chrome (and other browser CI systems), since
something in that huge matrix fails or times out for everyone.

#4934 suggests
splitting these into separate files. As a stopgap, split them out
using the WPT "variant" mechanism and provide expected failure files
for subsets, which should make fixing the tests and/or browsers more
actionable, and let us catch new regressions.

Bug: 930297
Change-Id: I4813281f547216b2b5f377118a58a419f62cfbc7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063808
Commit-Queue: Philip Jägenstedt <[email protected]>
Reviewed-by: Philip Jägenstedt <[email protected]>
Cr-Commit-Position: refs/heads/master@{#743019}
@inexorabletash
Copy link
Member

Chrome CL is in (thanks!) - @foolip can you admin merge?

@stephenmcgruer stephenmcgruer merged commit d408124 into master Feb 25, 2020
@stephenmcgruer stephenmcgruer deleted the chromium-export-cl-2063808 branch February 25, 2020 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants