[wpt-sync] Sync PR 39376 - Rewrite test to avoid nested promise_test calls
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox114 fixed)
| Tracking | Status | |
|---|---|---|
| firefox114 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 39376 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/39376
Details from upstream follow.
Chris Fredrickson <cfredric@chromium.org> wrote:
Rewrite test to avoid nested promise_test calls
This is an effort to make these tests as straightforward as possible,
to fix upstream flakiness. This CL removes the nested calls to
promise_test that occur in the iframe created by one of the top-level
tests, in favor of just running the iframe tests as top-level calls
to promise_test.Bug: 1429782
Change-Id: I52e0368d2522e29afe1f2cb5822fac010756e254
Reviewed-on: https://chromium-review.googlesource.com/4397961
WPT-Export-Revision: 16c9ebc545ef3dfd6dc0b8e088617111d943f4c5
| Assignee | ||
Comment 1•3 years ago
|
||
| Assignee | ||
Comment 2•3 years ago
|
||
| Assignee | ||
Comment 3•3 years ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 7 subtests
Status Summary
Firefox
OK : 1
FAIL: 7
Chrome
OK : 1
PASS: 7
Safari
OK : 1
FAIL: 7
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /top-level-storage-access-api/tentative/requestStorageAccessFor-insecure.sub.window.html [wpt.fyi]
- [top-level-context] document.requestStorageAccessFor() should be supported on the document interface:
FAIL(Chrome:PASS, Safari:FAIL) - [top-level-context] document.requestStorageAccessFor() should be rejected by default with no user gesture:
FAIL(Chrome:PASS, Safari:FAIL) - [non-fully-active] document.requestStorageAccessFor() should not resolve when run in a detached frame:
FAIL(Chrome:PASS, Safari:FAIL) - [non-fully-active] document.requestStorageAccessFor() should not resolve when run in a detached DOMParser document:
FAIL(Chrome:PASS, Safari:FAIL) - [frame-on-insecure-page] document.requestStorageAccessFor() should be supported on the document interface in embedded iframes:
FAIL(Chrome:PASS, Safari:FAIL) - [frame-on-insecure-page] document.requestStorageAccessFor() should be rejected when called in an iframe:
FAIL(Chrome:PASS, Safari:FAIL) - [top-level-context] document.requestStorageAccessFor() should be rejected when called in an insecure context:
FAIL(Chrome:PASS, Safari:FAIL)
- [top-level-context] document.requestStorageAccessFor() should be supported on the document interface:
Comment 5•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/8bddbc74448c
https://hg.mozilla.org/mozilla-central/rev/5c97264c007a
Description
•