Bug 162373 - Flaky Test: inspector/network/xhr-json-blob-has-content.html
Summary: Flaky Test: inspector/network/xhr-json-blob-has-content.html
Status: RESOLVED DUPLICATE of bug 162360
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: WebKit Commit Bot
Depends on:
Blocks: 50856
  Show dependency treegraph
Reported: 2016-09-21 21:03 PDT by WebKit Commit Bot
Modified: 2016-09-21 23:20 PDT (History)
5 users (show)

See Also:

Archive of layout-test-results from webkit-cq-02 (898.07 KB, application/zip)
2016-09-21 21:03 PDT, WebKit Commit Bot
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description WebKit Commit Bot 2016-09-21 21:03:34 PDT
This is an automatically generated bug from the commit-queue.
inspector/network/xhr-json-blob-has-content.html has been flaky on the commit-queue.

inspector/network/xhr-json-blob-has-content.html was authored by dcrousso+webkit@gmail.com and joepeck@webkit.org.

The commit-queue just saw inspector/network/xhr-json-blob-has-content.html flake (test timed out) while processing attachment 289510 [details] on bug 162353.
Bot: webkit-cq-02  Port: <class 'webkitpy.common.config.ports.MacPort'>  Platform: Mac OS X 10.10.5

The bots will update this with information from each new failure.

If you believe this bug to be fixed or invalid, feel free to close.  The bots will re-open if the flake re-occurs.

If you would like to track this test fix with another bug, please close this bug as a duplicate.  The bots will follow the duplicate chain when making future comments.
Comment 1 WebKit Commit Bot 2016-09-21 21:03:37 PDT
Created attachment 289515 [details]
Archive of layout-test-results from webkit-cq-02
Comment 2 Alexey Proskuryakov 2016-09-21 23:18:49 PDT
May have been fixed by rollout in r206249.
Comment 3 Alexey Proskuryakov 2016-09-21 23:20:01 PDT
I guess not, as it started earlier.

*** This bug has been marked as a duplicate of bug 162360 ***