Closed Bug 1585812 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 19480 - [fetch] Correct tentative tests

Categories

(Core :: DOM: Networking, task, P5)

task

Tracking

()

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream][necko-triaged])

Attachments

(2 files)

Sync web-platform-tests PR 19480 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/19480
Details from upstream follow.

Mike Pennisi <mike@mikepennisi.com> wrote:

[fetch] Correct tentative tests

This is in service of https://github.com/web-platform-tests/rfcs/pull/28

Component: web-platform-tests → DOM: Networking
Product: Testing → Core
Priority: P4 → P5
Whiteboard: [wptsync downstream] → [wptsync downstream][necko-triaged]
Whiteboard: [wptsync downstream][necko-triaged] → [wptsync downstream error][necko-triaged]
Whiteboard: [wptsync downstream error][necko-triaged] → [wptsync downstream][necko-triaged]
Whiteboard: [wptsync downstream][necko-triaged] → [wptsync downstream error][necko-triaged]
Whiteboard: [wptsync downstream error][necko-triaged] → [wptsync downstream][necko-triaged]
Whiteboard: [wptsync downstream][necko-triaged] → [wptsync downstream error][necko-triaged]
Whiteboard: [wptsync downstream error][necko-triaged] → [wptsync downstream][necko-triaged]
Whiteboard: [wptsync downstream][necko-triaged] → [wptsync downstream error][necko-triaged]
Whiteboard: [wptsync downstream error][necko-triaged] → [wptsync downstream][necko-triaged]
Result changes from PR not available.

GitHub CI Results

wpt.fyi PR Results Base Results

Ran 2 tests and 22 subtests

Firefox

OK : 1
PASS : 9
FAIL : 8
TIMEOUT: 2
NOTRUN : 3

Chrome

OK : 2
PASS : 20
FAIL : 1

Safari

OK : 1
PASS : 6
FAIL : 7
TIMEOUT: 2
NOTRUN : 6

Existing tests that now have a worse result

/fetch/metadata/redirect/redirect-https-downgrade.tentative.sub.html: Firefox: OK->TIMEOUT, Chrome: OK->OK, Safari: OK->TIMEOUT

Other new tests that's don't pass

/fetch/metadata/redirect/redirect-https-downgrade.tentative.sub.html
Https downgrade stylesheet: Firefox: TIMEOUT, Chrome: PASS, Safari: NOTRUN
Https downgrade font => No headers: Firefox: NOTRUN, Chrome: PASS, Safari: NOTRUN
Https downgrade prefetch => No headers: Firefox: FAIL, Chrome: PASS, Safari: MISSING
Https downgrade track: Firefox: NOTRUN, Chrome: PASS, Safari: NOTRUN
Https downgrade script => No headers: Firefox: FAIL, Chrome: FAIL, Safari: FAIL
Https downgrade image => No headers: Firefox: NOTRUN, Chrome: PASS, Safari: NOTRUN

/fetch/corb/script-resource-with-nonsniffable-types.tentative.sub.html
CORB blocks 'multipart/byteranges': Firefox: FAIL, Chrome: PASS, Safari: FAIL
CORB blocks 'application/gzip': Firefox: FAIL, Chrome: PASS, Safari: FAIL
CORB blocks 'application/x-protobuf': Firefox: FAIL, Chrome: PASS, Safari: FAIL
CORB blocks 'application/zip': Firefox: FAIL, Chrome: PASS, Safari: FAIL
CORB blocks 'text/event-stream': Firefox: FAIL, Chrome: PASS, Safari: FAIL
CORB blocks 'application/x-gzip': Firefox: FAIL, Chrome: PASS, Safari: FAIL

Gecko CI Results

Ran 2 tests and 21 subtests
OK : 1
PASS : 9
FAIL : 8
TIMEOUT: 2
NOTRUN : 3

Existing tests that now have a worse result

/fetch/metadata/redirect/redirect-https-downgrade.tentative.sub.html: TIMEOUT

New tests that don't pass

/fetch/corb/script-resource-with-nonsniffable-types.tentative.sub.html
CORB blocks 'application/gzip': FAIL
CORB blocks 'application/x-gzip': FAIL
CORB blocks 'application/x-protobuf': FAIL
CORB blocks 'application/zip': FAIL
CORB blocks 'multipart/byteranges': FAIL
CORB blocks 'text/event-stream': FAIL
/fetch/metadata/redirect/redirect-https-downgrade.tentative.sub.html
Https downgrade font => No headers: NOTRUN
Https downgrade image => No headers: NOTRUN
Https downgrade prefetch => No headers: FAIL
Https downgrade script => No headers: FAIL
Https downgrade stylesheet: TIMEOUT
Https downgrade track: NOTRUN

Automatic update from web-platform-tests
[fetch] Correct test bugs

Prior to this commit, this test referenced a non-existent binding while
generating subtest titles. This produced an uncaught exception in all
implementations. Currently, testharness.js interprets this result as a
failing "single-page test," although it will soon be more accurately
reported as a harness error [1].

Remove the unresolvable reference and improve the subtest title to more
accurately describe the behavior under test.

[1] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md

--
[fetch] Correct syntax error

--

wpt-commits: 285fcd938bc74cf4161c2ff7b84a0f274c0f1320, 7031c8cc58033312878636c8f973589946352385
wpt-pr: 19480

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e9d25072a478
[wpt PR 19480] - [fetch] Correct tentative tests, a=testonly
https://hg.mozilla.org/integration/autoland/rev/f3e99fd78d1d
[wpt PR 19480] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: