Bug 59488 - Flaky Test: fast/loader/file-protocol-fragment.html
Summary: Flaky Test: fast/loader/file-protocol-fragment.html
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other OS X 10.5
: P2 Normal
Assignee: WebKit Commit Bot
Depends on:
Blocks: 50856
  Show dependency treegraph
Reported: 2011-04-26 13:56 PDT by WebKit Commit Bot
Modified: 2011-04-26 18:29 PDT (History)
2 users (show)

See Also:

Failure diff from cr-jail-8 (843 bytes, text/plain)
2011-04-26 13:56 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 2011-04-26 13:56:21 PDT
This is an automatically generated bug from the commit-queue.
fast/loader/file-protocol-fragment.html has been flaky on the commit-queue.

fast/loader/file-protocol-fragment.html was authored by koivisto@iki.fi.

The commit-queue just saw fast/loader/file-protocol-fragment.html flake (Text diff mismatch) while processing attachment 90899 [details] on bug 58852.
Bot: cr-jail-8  Port: Mac  Platform: Mac OS X 10.6.6

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 2011-04-26 13:56:25 PDT
Created attachment 91151 [details]
Failure diff from cr-jail-8
Comment 2 Antti Koivisto 2011-04-26 14:53:14 PDT
This might help: http://trac.webkit.org/changeset/84962
Comment 3 Eric Seidel (no email) 2011-04-26 18:29:56 PDT
Thank you very much Antti!  You should also be aware, we appear to have some sort of maurauding http failrues.  It's unclear if we have an apache conig issue or what.  Some of our http tests which flake are definitely real failures (As this one may be), and some are definitely due to some underlying issue in our http testing setup.

Thanks again for the fix.