Closed Bug 1808094 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 37712 - Initialize long task reporting for ScriptPromiseResolver

Categories

(Core :: DOM: Performance, task, P4)

task

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Noam Rosenthal <nrosenthal@chromium.org> wrote:

Initialize long task reporting for ScriptPromiseResolver

This tells the PerformanceMonitor to report longtasks
in promise chains that were not started from a callback,
e.g. fetch().then(() => {...long_task})

Bug: 1251964
Change-Id: I745780f834f9d1dfc8e8a5c8295326f06276cba6
Reviewed-on: https://chromium-review.googlesource.com/4129480
WPT-Export-Revision: 792c72bdc72e7c3659cebe5a2a83ba5dcc4ab4a9

Component: web-platform-tests → DOM: Performance
Product: Testing → Core

CI Results

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

Total 13 tests and 1 subtests

Status Summary

Firefox

OK : 11
FAIL : 18
ERROR : 2

Chrome

OK : 12
PASS : 15
TIMEOUT: 2
NOTRUN : 4

Safari

OK : 11
FAIL : 18
ERROR : 2

Links

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/500899dd671f [wpt PR 37712] - Initialize long task reporting for ScriptPromiseResolver, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.