1243266 - Intermittent TEST-UNEXPECTED-TIMEOUT | /_mozilla/service-workers/service-worker/navigation-redirect.https.html | Redirect to other-origin in-scope with opaque redirect response which is passed through Cache. - Test timed out

Status: RESOLVED WORKSFORME

(Testing :: web-platform-tests, defect)

Description

[Phil Ringnalda (:philor)]

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

Comment 1

[Intermittent Failures Robot]

5 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 3
* mozilla-central: 1
* fx-team: 1

Platform breakdown:
* linux32: 3
* windows8-64: 1
* windows7-32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1243266&startday=2016-04-25&endday=2016-05-01&tree=all

Comment 2

[Intermittent Failures Robot]

5 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 3
* fx-team: 2

Platform breakdown:
* linux32: 4
* windows7-32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1243266&startday=2016-05-10&endday=2016-05-16&tree=all

Comment 3

[Josh Matthews [:jdm]]

I caught this in rr, and it looked like the fetch for the response that gets stored in the cache was in progress when the timeout occurred. This should be taken with a grain of salt, since it was a debug build running under rr, but it might be worth doing more exploration with rr.