Files
tubestation/testing/web-platform/tests/server-timing/idlharness.https.any.js
Stephen McGruer cc807f3431 Bug 1623736 [wpt PR 22344] - Mark two idlharness tests as timeout=long, a=testonly
Automatic update from web-platform-tests
Mark two idlharness tests as timeout=long

On Chromium CI these are occasionally spiking to 7s, causing timeouts.

Bug: 1062667
Change-Id: Ib4d21732c74c14b83b492945314813eff0f8c36b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2110523
Commit-Queue: Robert Ma <robertma@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#752016}

--

wpt-commits: 374da1f35d59a6d5678e67ac4c44bc9b849efe11
wpt-pr: 22344
2020-03-26 11:39:52 +00:00

30 lines
775 B
JavaScript

// META: script=/resources/WebIDLParser.js
// META: script=/resources/idlharness.js
// META: timeout=long
'use strict';
// https://w3c.github.io/server-timing/
idl_test(
['resource-timing', 'server-timing'],
['performance-timeline', 'hr-time', 'dom'],
idl_array => new Promise((resolve, reject) => {
new PerformanceObserver(entries => {
entries.getEntries().forEach(e => {
if (!e.name.endsWith('blue.png'))
return;
self.resource = e;
self.server = e.serverTiming[0];
idl_array.add_objects({
PerformanceResourceTiming: ['resource'],
PerformanceServerTiming: ['server']
});
resolve();
})
}).observe({entryTypes: ['resource']});
fetch('resources/blue.png');
})
);