Closed Bug 1509130 Opened 6 years ago Closed 5 years ago

[wpt-sync] Sync PR 14167 - Align resource timing buffer full processing to spec PR 168

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla66
Tracking Flags:
Tracking Status
firefox66 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream]) 

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

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

Yoav Weiss <yoavweiss@chromium.org> wrote:
>  Align resource timing buffer full processing to spec PR 168
>  
>  This change implements the processing model from PR 168[1], when
>  it comes to setResourceTimingBufferSize(), clearResourceTimings()
>  and the firing of the resourcetimingbufferfull event.
>  
>  [1] https://github.com/w3c/resource-timing/pull/168
>  
>  Change-Id: I3a57196f10e0b4cf2bae5662b0e075673a0c2d80
>  Reviewed-on: https://chromium-review.googlesource.com/1345269
>  WPT-Export-Revision: 89396bd1e0b9183695891bac9037b4c75f137ec3
Component: web-platform-tests → DOM
Product: Testing → Core
Ran 12 tests and 26 subtests
OK     : 10[linux32-debug,linux32-opt], 11[linux64-debug,linux64-opt]
PASS   : 17
FAIL   : 6
TIMEOUT: 3
ERROR  : 1[linux32-debug,linux32-opt]
NOTRUN : 1

Existing tests that now have a worse result (e.g. they used to PASS and now FAIL):
/service-workers/service-worker/performance-timeline.https.html: TIMEOUT
    Resource Timing: TIMEOUT
    Test Performance Timeline API in Service Worker: TIMEOUT
    empty service worker fetch event included in performance timings: NOTRUN

New tests that have failures or other problems:
/resource-timing/buffer-full-add-then-clear.html
    Verify that adding entries and then clearing the resource timing buffer results in entries added in the right order: FAIL
/resource-timing/buffer-full-inspect-buffer-during-callback.html: ERROR[linux32-debug,linux32-opt]
    Verify that inspecting the resource timing buffer during resourcetimingbufferfull call doesn't exceed the limit.: FAIL
/resource-timing/buffer-full-set-to-current-buffer.html
    Check result: FAIL
/resource-timing/buffer-full-store-and-clear-during-callback.html
    Verify that clearing the resource timing buffer and storing the entries during resourcetimingbufferfull call works: FAIL
/resource-timing/buffer-full-then-increased.html
    Verify that adding entries and then increasing the size of the resource timing buffer results in entries added in the right order: FAIL
/resource-timing/buffer-full-when-populate-entries.html
    Verify that resourcetimingbufferfull is properly invoked: FAIL
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/978c4475bce2
[wpt PR 14167] - Align resource timing buffer full processing to spec PR 168, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/ae1b488dbc16
[wpt PR 14167] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/01034b130bc6
[wpt PR 14167] - Align resource timing buffer full processing to spec PR 168, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/d1b59860e1d3
[wpt PR 14167] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/01034b130bc6
https://hg.mozilla.org/mozilla-central/rev/d1b59860e1d3
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox66: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.