Closed Bug 1831664 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39870 - [wptrunner] Use `pageLoadStrategy: eager` for testharness on `chrome`

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 39870 into mozilla-central (this bug is closed when the sync is complete).

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

Jonathan Lee <jonathanjlee@google.com> wrote:

[wptrunner] Use pageLoadStrategy: eager for testharness on chrome

chromedriver support for eager pageloads shipped in M77: https://chromedriver.storage.googleapis.com/77.0.3865.10/notes.txt

See also: crrev.com/c/1241213/5/chrome/test/chromedriver/capabilities.cc#202

Test: ./run_wpt_tests.py -t Default badging --product=chrome

PR 39870 applied with additional changes from upstream: 3cc3f5123a8a092697490c66e6c69cf614523d87
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Try push failed: decision task Axx2IPqpSSaVcnmAO2ruwg returned error
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1711cf1c775b [wpt PR 39870] - [wptrunner] Remove obsolete testharness `supports_eager_pageload=False` workaround, a=testonly
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in before you can comment on or make changes to this bug.