Open Bug 1331948 Opened 3 years ago Updated 3 years ago

resource_connection_reuse.html test is unstable

Categories

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

defect
Not set

Tracking

(firefox53 fixed)

REOPENED
mozilla53
Tracking Status
firefox53 --- fixed

People

(Reporter: jgraham, Unassigned)

Details

It seems like sometimes fetchStart and connectStart are not the same when the test expects them to be. I'm not enough of an expert to determine if this is an unreasonable test or not.
Flags: needinfo?(valentin.gosu)
The .getEntriesByType('resource') call returns 2 entries.
When the test fails, the first one has the same fetchStart and connectStart. The second one doesn't.
The test assumes that the fetch that is reusing the connection will be the last one to complete, and the last one in the array. [1] That doesn't always seem to be the case.

[1] https://github.com/w3c/web-platform-tests/pull/4266#discussion_r90321665
Flags: needinfo?(valentin.gosu)
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8ab843673764
Disable unstable resourceTiming test, a=testonly
https://hg.mozilla.org/mozilla-central/rev/8ab843673764
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
You need to log in before you can comment on or make changes to this bug.