Bug 142683 - fast/dom/webtiming.html is flaky
Summary: fast/dom/webtiming.html is flaky
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-13 16:17 PDT by Alexey Proskuryakov
Modified: 2015-03-16 10:45 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2015-03-13 16:17:59 PDT 
fast/dom/webtiming.html often fails on all Yosemite bots:

-PASS timing.domainLookupStart is >= timing.fetchStart
+FAIL timing.domainLookupStart should be >= timing.fetchStart. Was 1426042727967 (of type number).

https://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=fast%2Fdom%2Fwebtiming.html
Comment 1 Alex Christensen 2015-03-16 10:31:15 PDT 
(In reply to comment #0)
Is there any way to find when this started being flaky?  I haven't touched this code for about 6 months.
I'm not sure what would cause this.  My initial thought is we're getting bad data from CFNetwork, but that seems unlikely unless libsoup has the exact same problem.  Are we doing something strange with the domain lookup in WebCore?
Comment 2 Alexey Proskuryakov 2015-03-16 10:45:07 PDT 
I'm not sure if Soup based ports have the same problem, the diff was not the same in instance that I checked.