Closed Bug 1861243 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42755 - Add long timeout to pagereveal WPT

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
121 Branch
Tracking Status
firefox121 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

David Bokan <bokan@chromium.org> wrote:

Add long timeout to pagereveal WPT

This test runs very close to the timeout in firefox. Other tests(*)
using the runBfcacheTest framework also seem to be long and are marked
long so doing this here too.

  • html/browsers/browsing-the-web/back-forward-cache/eligibility/shared-worker.html
  • html/browsers/browsing-the-web/back-forward-cache/pushstate.https.html

Bug: 1466250,1495795
Change-Id: I524b4d3358509a6614356c68dfa406bc32d9fc6a

Reviewed-on: https://chromium-review.googlesource.com/4974354
WPT-Export-Revision: 48de8c39deb8cd0ed854687d4b0ae3c87d87a6dd

PR 42755 applied with additional changes from upstream: 21dc7156fbd1e6a6e24eece7a1159e1c1913560d
Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
PASS: 1

Safari

OK : 1
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/79ad8bc72229 [wpt PR 42755] - Add long timeout to pagereveal WPT, a=testonly https://hg.mozilla.org/integration/autoland/rev/1afc88c98a0a [wpt PR 42755] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in before you can comment on or make changes to this bug.