Closed Bug 1526899 Opened 7 years ago Closed 6 years ago

Intermittent /resource-timing/resource-timing-level1.sub.html | 'xmlhttprequest 250ms delay in headers does not affect responseStart' - assert_greater_than_equal: Delay after HTTP/1.1 status should not affect 'responseStart'

Categories

(Core :: DOM: Core & HTML, defect, P5)

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

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1527172

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, regression)

#[markdown(off)]
Filed by: cbrindusan [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=227589510&repo=mozilla-central

https://queue.taskcluster.net/v1/task/S8HGgPTqSLOP_RJLBtTfPw/runs/0/artifacts/public/logs/live_backing.log

[task 2019-02-11T10:58:09.207Z] 10:58:09 INFO - TEST-START | /resource-timing/resource-timing-level1.sub.html
[task 2019-02-11T10:58:09.215Z] 10:58:09 INFO - Closing window 82
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO -
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'link (Potentially Cached): Immediately fetch the same URL, exercising the cache hit path (if any).
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'iframe: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'.
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'xmlhttprequest: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'.
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'script: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'.
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'link: 250ms delay before 'responseStart', another 250ms delay before 'responseEnd'.
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'iframe (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'.
[task 2019-02-11T10:58:36.810Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'xmlhttprequest (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'.
[task 2019-02-11T10:58:36.811Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'script (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'.
[task 2019-02-11T10:58:36.811Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'link (Redirected): 250ms delay before 'redirectEnd', another 250ms delay before 'responseStart'.
[task 2019-02-11T10:58:36.811Z] 10:58:36 INFO - TEST-PASS | /resource-timing/resource-timing-level1.sub.html | 'iframe 250ms delay in headers does not affect responseStart'
[task 2019-02-11T10:58:36.811Z] 10:58:36 INFO - TEST-UNEXPECTED-FAIL | /resource-timing/resource-timing-level1.sub.html | 'xmlhttprequest 250ms delay in headers does not affect responseStart' - assert_greater_than_equal: Delay after HTTP/1.1 status should not affect 'responseStart'. expected a number greater than or equal to 20270 but got 20260

Component: DOM → DOM: Core & HTML
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.