Closed Bug 1830956 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 39806 - resolve to config promise

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox115 fixed)

RESOLVED FIXED
115 Branch
Tracking Status
firefox115 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Liam Brady <lbrady@google.com> wrote:

resolve to config promise

Change-Id: I03f6b904e28d15216c03f1295e857860fbdf9b6f
Reviewed-on: https://chromium-review.googlesource.com/4499266
WPT-Export-Revision: 6b64b03c8180af7df281b10f182ea2b73ae3072a

Try push failed: decision task Ug7m4fTvQleU8wfsCiyYjw returned error

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 4 subtests

Status Summary

Firefox

OK : 1
FAIL: 4

Chrome

OK : 1
FAIL: 4

Safari

OK : 1
FAIL: 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /fenced-frame/resolve-to-config-promise.https.html [wpt.fyi]
    • resolveToConfig set to a promise that resolves to true: FAIL (Chrome: FAIL, Safari: FAIL)
    • resolveToConfig set to a promise that resolves to false: FAIL (Chrome: FAIL, Safari: FAIL)
    • resolveToConfig set to a promise that immediately resolves: FAIL (Chrome: FAIL, Safari: FAIL)
    • resolveToConfig set to a promise that resolves to an invalid value: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c313ea935956 [wpt PR 39806] - Let resolveToConfig take a promise., a=testonly https://hg.mozilla.org/integration/autoland/rev/f8c0670ac89f [wpt PR 39806] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in before you can comment on or make changes to this bug.