Closed
Bug 1772567
Opened 3 years ago
Closed 3 years ago
[wpt-sync] Sync PR 34301 - Revert "Revamp object-not-found redirect resource timing tests"
Categories
(Core :: Performance: General, task, P4)
Core
Performance: General
Tracking
()
RESOLVED
FIXED
103 Branch
| Tracking | Status | |
|---|---|---|
| firefox103 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 34301 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/34301
Details from upstream follow.
Igor Ruvinov <igorruvinov@chromium.org> wrote:
Revert "Revamp object-not-found redirect resource timing tests"
This reverts commit f1fda133e0491f023d674167e36e04bd1da4061b.
Reason for revert: likely caused linux-bfcache-rel CI failures.
Example failure:
https://ci.chromium.org/ui/p/chromium/builders/ci/linux-bfcache-rel/33293/overviewOriginal change's description:
Revamp object-not-found redirect resource timing tests
I suspect that the object resource timing tests are flakily timing out
due to flakiness in \<object>'s events themselves.This CL moves these tests to the more recent resource timing testing
infrastructure, and also ends the test once a PerformanceObserver runs
its callback.Bug: 1318592
Change-Id: I2b01188756b212b51b8c8d095a2257d4a0e54e91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3682424
Commit-Queue: Yoav Weiss \<yoavweiss@chromium.org>
Reviewed-by: Ian Clelland \<iclelland@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1010553}Bug: 1332556, 1318592
Change-Id: I99dc11ffa01158bcd2c0e1814ff5df4c3a158d7d
No-Presubmit: true
No-Tree-Checks: true
No-Try: trueReviewed-on: https://chromium-review.googlesource.com/3688576
WPT-Export-Revision: fd9871c5744fa1af25a038ff3ed1408e2d8b9f57
|
Assignee | |
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
|
|
Assignee | |
Updated•3 years ago
|
Component: web-platform-tests → Performance
Product: Testing → Core
|
|
Assignee | |
Updated•3 years ago
|
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
|
|
Assignee | |
Comment 1•3 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=105d7187e6ee137caab3f3f43e21993d578e373b
|
|
Assignee | |
Comment 2•3 years ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 45 tests and 2 subtests
Status Summary
Firefox
OK : 37
PASS : 74
FAIL : 22
TIMEOUT: 13
ERROR : 2
NOTRUN : 81
Chrome
OK : 42
PASS : 179
TIMEOUT: 4
ERROR : 1
NOTRUN : 3
Safari
OK : 34
PASS : 40
FAIL : 37
TIMEOUT: 18
ERROR : 2
NOTRUN : 92
Links
Details
Firefox-only Failures
- /resource-timing/SO-XO-SO-redirect-chain-tao.https.html [wpt.fyi]
- Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have no
Timing-Allow-Origin:headers.:FAIL
- Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have no
- /resource-timing/buffer-full-add-after-full-event.html [wpt.fyi]:
TIMEOUT- Test that entry was added to the buffer after a buffer full event:
TIMEOUT
- Test that entry was added to the buffer after a buffer full event:
- /resource-timing/buffer-full-add-then-clear.html [wpt.fyi]
- Test that if the buffer is cleared after entries were added to the secondary buffer, those entries make it into the primary one:
FAIL
- Test that if the buffer is cleared after entries were added to the secondary buffer, those entries make it into the primary one:
- /resource-timing/buffer-full-then-increased.html [wpt.fyi]
- Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event:
FAIL
- Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event:
- /resource-timing/buffer-full-when-populate-entries.html [wpt.fyi]:
ERROR- Test that a buffer full event does not bubble and that resourcetimingbufferfull is called only once per overflow:
FAIL
- Test that a buffer full event does not bubble and that resourcetimingbufferfull is called only once per overflow:
- /resource-timing/cross-origin-redirects.html [wpt.fyi]:
TIMEOUT- Verify that cross-origin resources' timings aren't exposed through HTTP redirects.:
TIMEOUT - Verify that a redirected cross-origin resources' timings aren't exposed when the TAO check fails.:
NOTRUN - Verify that cross-origin resources' timings are exposed when the TAO check succeeds. Also verify that secureConnectionStart is 0 since the original request was over HTTP.:
NOTRUN - Verify that a redirect chain through cross-origin resources have their timings exposed when all TAO checks succeed. Also verify that secureConnectionStart is 0 since the original request was over HTTP.:
NOTRUN
- Verify that cross-origin resources' timings aren't exposed through HTTP redirects.:
- /resource-timing/iframe-redirect-without-location.html [wpt.fyi]:
TIMEOUT - /resource-timing/nextHopProtocol-is-tao-protected.https.html [wpt.fyi]
- Fetch TAO-less font from remote origin. Make sure nextHopProtocol is the empty string.:
FAIL
- Fetch TAO-less font from remote origin. Make sure nextHopProtocol is the empty string.:
New Tests That Don't Pass
- /resource-timing/SO-XO-SO-redirect-chain-tao.https.html [wpt.fyi]
- Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have no
Timing-Allow-Origin:headers.:FAIL(Chrome:PASS, Safari:PASS) - Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have
Timing-Allow-Origin:headers only on some of the responses.:FAIL(Chrome:PASS, Safari:FAIL) - Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have
Timing-Allow-Origin:headers with a specific origin.:FAIL(Chrome:PASS, Safari:FAIL)
- Verify that cross origin resources' timings are not exposed when same-origin=>cross-origin=>same-origin redirects have no
- /resource-timing/TAO-match.html [wpt.fyi]:
TIMEOUT(Chrome:OK, Safari:TIMEOUT)- The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only the origin. (iframe):
TIMEOUT(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only a wildcard. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a case-sensitive match. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains the origin and a wildcard. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a wildcard. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value list contains a null origin. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains multiple wildcards. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains only the uppercased origin. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains the origin, a space, then a wildcard. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header is not present. (iframe):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only the origin. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only a wildcard. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a case-sensitive match. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains the origin and a wildcard. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a wildcard. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value list contains a null origin. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains multiple wildcards. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains only the uppercased origin. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains the origin, a space, then a wildcard. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header is not present. (image):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only the origin. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only a wildcard. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a case-sensitive match. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains the origin and a wildcard. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a wildcard. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value list contains a null origin. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains multiple wildcards. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains only the uppercased origin. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains the origin, a space, then a wildcard. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header is not present. (script):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only the origin. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only a wildcard. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a case-sensitive match. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains the origin and a wildcard. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a wildcard. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value list contains a null origin. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains multiple wildcards. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains only the uppercased origin. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains the origin, a space, then a wildcard. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header is not present. (stylesheet):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only the origin. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only a wildcard. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a case-sensitive match. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains the origin and a wildcard. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains a wildcard. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value list contains a null origin. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will pass when the Timing-Allow-Origin header value list contains multiple wildcards. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains only the uppercased origin. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header value contains the origin, a space, then a wildcard. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN) - The timing allow check algorithm will fail when the Timing-Allow-Origin header is not present. (XMLHttpRequest):
NOTRUN(Chrome:PASS, Safari:NOTRUN)
- The timing allow check algorithm will pass when the Timing-Allow-Origin header value contains only the origin. (iframe):
- /resource-timing/buffer-full-add-after-full-event.html [wpt.fyi]:
TIMEOUT(Chrome:OK, Safari:OK)- Test that entry was added to the buffer after a buffer full event:
TIMEOUT(Chrome:PASS, Safari:PASS)
- Test that entry was added to the buffer after a buffer full event:
- /resource-timing/buffer-full-add-then-clear.html [wpt.fyi]
- Test that if the buffer is cleared after entries were added to the secondary buffer, those entries make it into the primary one:
FAIL(Chrome:PASS, Safari:PASS)
- Test that if the buffer is cleared after entries were added to the secondary buffer, those entries make it into the primary one:
- /resource-timing/buffer-full-then-increased.html [wpt.fyi]
- Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event:
FAIL(Chrome:PASS, Safari:PASS)
- Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event:
- /resource-timing/buffer-full-when-populate-entries.html [wpt.fyi]:
ERROR(Chrome:OK, Safari:OK)- Test that a buffer full event does not bubble and that resourcetimingbufferfull is called only once per overflow:
FAIL(Chrome:PASS, Safari:PASS)
- Test that a buffer full event does not bubble and that resourcetimingbufferfull is called only once per overflow:
- /resource-timing/cross-origin-redirects.html [wpt.fyi]:
TIMEOUT(Chrome:OK, Safari:OK)- Verify that cross-origin resources' timings aren't exposed through HTTP redirects.:
TIMEOUT(Chrome:PASS, Safari:PASS) - Verify that a redirected cross-origin resources' timings aren't exposed when the TAO check fails.:
NOTRUN(Chrome:PASS, Safari:PASS) - Verify that cross-origin resources' timings are exposed when the TAO check succeeds. Also verify that secureConnectionStart is 0 since the original request was over HTTP.:
NOTRUN(Chrome:PASS, Safari:PASS) - Verify that a redirect chain through cross-origin resources have their timings exposed when all TAO checks succeed. Also verify that secureConnectionStart is 0 since the original request was over HTTP.:
NOTRUN(Chrome:PASS, Safari:PASS) - Verify that a redirect chain through cross-origin resources do not have their timings exposed when any of the TAO checks fail. (FAIL -> FAIL -> FAIL):
NOTRUN(Chrome:PASS, Safari:FAIL) - Verify that a redirect chain through cross-origin resources do not have their timings exposed when any of the TAO checks fail. (FAIL -> FAIL -> PASS):
NOTRUN(Chrome:PASS, Safari:FAIL) - Verify that a redirect chain through cross-origin resources do not have their timings exposed when any of the TAO checks fail. (FAIL -> PASS -> FAIL):
NOTRUN(Chrome:PASS, Safari:FAIL) - Verify that a redirect chain through cross-origin resources do not have their timings exposed when any of the TAO checks fail. (FAIL -> PASS -> PASS):
NOTRUN(Chrome:PASS, Safari:FAIL) - Verify that a redirect chain through cross-origin resources do not have their timings exposed when any of the TAO checks fail. (PASS -> FAIL -> FAIL):
NOTRUN(Chrome:PASS, Safari:FAIL) - Verify that a redirect chain through cross-origin resources do not have their timings exposed when any of the TAO checks fail. (PASS -> FAIL -> PASS):
NOTRUN(Chrome:PASS, Safari:FAIL) - Verify that a redirect chain through cross-origin resources do not have their timings exposed when any of the TAO checks fail. (PASS -> PASS -> FAIL):
NOTRUN(Chrome:PASS, Safari:FAIL)
- Verify that cross-origin resources' timings aren't exposed through HTTP redirects.:
- /resource-timing/entries-for-network-errors.sub.https.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:TIMEOUT)- A ResourceTiming entry should be created for network error of type non-HTTP redirect:
FAIL(Chrome:PASS, Safari:NOTRUN) - A ResourceTiming entry should be created for network error of type DNS failure:
FAIL(Chrome:PASS, Safari:NOTRUN) - A ResourceTiming entry should be created for network error of type Mixed content:
TIMEOUT(Chrome:TIMEOUT, Safari:NOTRUN) - A ResourceTiming entry should be created for network error of type only-if-cached resource that was not cached:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN) - A ResourceTiming entry should be created for network error of type too many redirects:
NOTRUN(Chrome:NOTRUN, Safari:NOTRUN)
- A ResourceTiming entry should be created for network error of type non-HTTP redirect:
- /resource-timing/iframe-failed-commit.html [wpt.fyi]:
ERROR(Chrome:ERROR, Safari:ERROR)- Test iframe from non-existent host gets reported:
TIMEOUT(Chrome:PASS, Safari:TIMEOUT) - Test iframe redirecting to non-existent host gets reported:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Same-origin iframe that complies with CSP attribute gets reported:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Same-origin iframe that doesn't comply with CSP attribute gets reported:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Cross-origin iframe that complies with CSP attribute gets reported:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Cross-origin iframe that doesn't comply with CSP attribute gets reported:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Same-origin empty iframe with a 200 status gets reported:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Cross-origin empty iframe with a 200 status gets reported:
NOTRUN(Chrome:PASS, Safari:NOTRUN)
- Test iframe from non-existent host gets reported:
- /resource-timing/iframe-redirect-without-location.html [wpt.fyi]:
TIMEOUT(Chrome:OK, Safari:OK)- Iframes should report resource timing for redirect responses without a location:
TIMEOUT(Chrome:PASS, Safari:FAIL)
- Iframes should report resource timing for redirect responses without a location:
- /resource-timing/initiator-type/dynamic-insertion.html [wpt.fyi]
- A font should have the 'css' initiator type.:
FAIL(Chrome:PASS, Safari:TIMEOUT)
- A font should have the 'css' initiator type.:
- /resource-timing/nextHopProtocol-is-tao-protected.https.html [wpt.fyi]:
TIMEOUT(Chrome:OK, Safari:TIMEOUT)- Fetch TAO-less font from remote origin. Make sure nextHopProtocol is the empty string.:
FAIL(Chrome:PASS, Safari:PASS) - Fetch TAO-less iframe from remote origin. Make sure nextHopProtocol is the empty string.:
TIMEOUT(Chrome:PASS, Safari:NOTRUN) - Fetch TAO'd iframe from remote origin. Make sure nextHopProtocol is not the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO-less image from remote origin. Make sure nextHopProtocol is the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO'd image from remote origin. Make sure nextHopProtocol is not the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO-less object from remote origin. Make sure nextHopProtocol is the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO'd object from remote origin. Make sure nextHopProtocol is not the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO-less script from remote origin. Make sure nextHopProtocol is the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO'd script from remote origin. Make sure nextHopProtocol is not the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO-less stylesheet from remote origin. Make sure nextHopProtocol is the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO'd stylesheet from remote origin. Make sure nextHopProtocol is not the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO-less synchronous xhr from remote origin. Make sure nextHopProtocol is the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO'd synchronous xhr from remote origin. Make sure nextHopProtocol is not the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO-less asynchronous xhr from remote origin. Make sure nextHopProtocol is the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN) - Fetch TAO'd asynchronous xhr from remote origin. Make sure nextHopProtocol is not the empty string.:
NOTRUN(Chrome:PASS, Safari:NOTRUN)
- Fetch TAO-less font from remote origin. Make sure nextHopProtocol is the empty string.:
- /resource-timing/same-origin-from-cross-origin-redirect.html [wpt.fyi]
- Verify that cross origin resources' timings are exposed when the final resource at the end of an HTTP redirect chain is same-origin.:
FAIL(Chrome:PASS, Safari:FAIL)
- Verify that cross origin resources' timings are exposed when the final resource at the end of an HTTP redirect chain is same-origin.:
- /resource-timing/sizes-cache.any.html [wpt.fyi]
- PerformanceResourceTiming sizes caching test:
FAIL(Chrome:PASS, Safari:FAIL)
- PerformanceResourceTiming sizes caching test:
- /resource-timing/sizes-cache.any.sharedworker.html [wpt.fyi]
- PerformanceResourceTiming sizes caching test:
FAIL(Chrome:PASS, Safari:FAIL)
- PerformanceResourceTiming sizes caching test:
- /resource-timing/sizes-cache.any.worker.html [wpt.fyi]
- PerformanceResourceTiming sizes caching test:
FAIL(Chrome:PASS, Safari:FAIL)
- PerformanceResourceTiming sizes caching test:
- /resource-timing/sizes-cache.any.serviceworker.html [wpt.fyi]
- PerformanceResourceTiming sizes caching test:
FAIL(Chrome:PASS, Safari:FAIL)
- PerformanceResourceTiming sizes caching test:
- /resource-timing/sizes-redirect-img.html [wpt.fyi]
- PerformanceResourceTiming sizes redirect image - direct URL:
FAIL(Chrome:PASS, Safari:FAIL) - PerformanceResourceTiming sizes redirect image - same origin redirect:
FAIL(Chrome:PASS, Safari:FAIL) - PerformanceResourceTiming sizes redirect image - cross origin redirect:
FAIL(Chrome:PASS, Safari:FAIL) - PerformanceResourceTiming sizes redirect image - cross origin to same origin redirect:
FAIL(Chrome:PASS, Safari:FAIL) - PerformanceResourceTiming sizes redirect image - same origin to remote origin to same origin redirect:
FAIL(Chrome:PASS, Safari:FAIL)
- PerformanceResourceTiming sizes redirect image - direct URL:
- /resource-timing/workerStart-tao-protected.https.html [wpt.fyi]
- A resource from a cross-origin service worker must not expose workerStart when there is a TAO failure:
FAIL(Chrome:PASS, Safari:FAIL) - A resource from a cross-origin service worker must expose workerStart when there is a TAO match:
FAIL(Chrome:PASS, Safari:FAIL)
- A resource from a cross-origin service worker must not expose workerStart when there is a TAO failure:
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8335ddf9bd7b
[wpt PR 34301] - Revert "Revamp object-not-found redirect resource timing tests", a=testonly
Status: REOPENED → RESOLVED
Closed: 3 years ago → 3 years ago
status-firefox103:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•