Closed Bug 1410064 Opened 7 years ago Closed 3 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | /service-workers/service-worker/client-navigate.https.html | Frame location should not be accessible after cross-origin navigation - Test timed out

Categories

(Core :: DOM: Service Workers, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Recent failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=158981924&repo=mozilla-inbound&lineNumber=4131

[task 2018-01-28T23:03:42.886Z] 23:03:42     INFO - TEST-START | /service-workers/service-worker/client-navigate.https.html
[task 2018-01-28T23:03:52.981Z] 23:03:52     INFO - 
[task 2018-01-28T23:03:52.982Z] 23:03:52     INFO - TEST-PASS | /service-workers/service-worker/client-navigate.https.html | Frame location should update on successful navigation 
[task 2018-01-28T23:03:52.982Z] 23:03:52     INFO - TEST-PASS | /service-workers/service-worker/client-navigate.https.html | Frame location should not be accessible after redirect 
[task 2018-01-28T23:03:52.982Z] 23:03:52     INFO - TEST-UNEXPECTED-TIMEOUT | /service-workers/service-worker/client-navigate.https.html | Frame location should not be accessible after cross-origin navigation - Test timed out
[task 2018-01-28T23:03:52.983Z] 23:03:52     INFO - 
[task 2018-01-28T23:03:52.985Z] 23:03:52     INFO - TEST-UNEXPECTED-NOTRUN | /service-workers/service-worker/client-navigate.https.html | Frame location should not update on failed about:blank navigation - expected PASS
[task 2018-01-28T23:03:52.985Z] 23:03:52     INFO - 
[task 2018-01-28T23:03:52.985Z] 23:03:52     INFO - TEST-UNEXPECTED-NOTRUN | /service-workers/service-worker/client-navigate.https.html | Frame location should not update on failed mixed-content navigation - expected PASS
[task 2018-01-28T23:03:52.985Z] 23:03:52     INFO - TEST-UNEXPECTED-TIMEOUT | /service-workers/service-worker/client-navigate.https.html | expected OK
[task 2018-01-28T23:03:52.985Z] 23:03:52     INFO - TEST-INFO took 10094ms
[task 2018-01-28T23:03:53.143Z] 23:03:53     INFO - PID 12107 | *** UTM:SVC TimerManager:registerTimer called after profile-before-change notification. Ignoring timer registration for id: telemetry_modules_ping
[task 2018-01-28T23:03:53.445Z] 23:03:53     INFO - Browser exited with return code 0
[task 2018-01-28T23:03:53.446Z] 23:03:53  WARNING - u'runner_teardown': ()
[task 2018-01-28T23:03:53.467Z] 23:03:53     INFO - Setting up ssl
[task 2018-01-28T23:03:53.508Z] 23:03:53     INFO - certutil | 
[task 2018-01-28T23:03:53.544Z] 23:03:53     INFO - certutil | 
[task 2018-01-28T23:03:53.572Z] 23:03:53     INFO - certutil | 
[task 2018-01-28T23:03:53.573Z] 23:03:53     INFO - Certificate Nickname                                         Trust Attributes
[task 2018-01-28T23:03:53.573Z] 23:03:53     INFO -                                                              SSL,S/MIME,JAR/XPI
[task 2018-01-28T23:03:53.574Z] 23:03:53     INFO - 
[task 2018-01-28T23:03:53.574Z] 23:03:53     INFO - web-platform-tests                                           CT,, 
[task 2018-01-28T23:03:53.574Z] 23:03:53     INFO - 
[task 2018-01-28T23:03:53.596Z] 23:03:53     INFO - Application command: /builds/worker/workspace/build/application/firefox/firefox --marionette about:blank -profile /tmp/tmpF9Gq3Y.mozrunner
[task 2018-01-28T23:03:53.624Z] 23:03:53     INFO - Starting runner
[task 2018-01-28T23:03:55.206Z] 23:03:55     INFO - PID 12411 | 1517180635197	Marionette	INFO	Listening on port 2828
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Component: web-platform-tests → DOM: Service Workers
Product: Testing → Core
Version: Version 3 → Trunk
See Also: → 1297923

Bulk closing some old intermittents.

Status: REOPENED → RESOLVED
Closed: 6 years ago3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.