Bug 166646 - Flaky Test: http/tests/security/cross-origin-xsl-redirect-BLOCKED.html
Summary: Flaky Test: http/tests/security/cross-origin-xsl-redirect-BLOCKED.html
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: 2017-01-03 02:58 PST by WebKit Commit Bot
Modified: 2017-01-03 16:15 PST (History)
6 users (show)

See Also:

Archive of layout-test-results from webkit-cq-01 (965.60 KB, application/zip)
2017-01-03 02:58 PST, 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 2017-01-03 02:58:30 PST
This is an automatically generated bug from the commit-queue.
http/tests/security/cross-origin-xsl-redirect-BLOCKED.html has been flaky on the commit-queue.

http/tests/security/cross-origin-xsl-redirect-BLOCKED.html was authored by jochen@chromium.org and rniwa@webkit.org.

The commit-queue just saw http/tests/security/cross-origin-xsl-redirect-BLOCKED.html flake (DumpRenderTree crashed) while processing attachment 297902 [details] on bug 166632.
Bot: webkit-cq-01  Port: <class 'webkitpy.common.config.ports.MacPort'>  Platform: Mac OS X 10.11.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 2017-01-03 02:58:34 PST
Created attachment 297929 [details]
Archive of layout-test-results from webkit-cq-01
Comment 2 Alexey Proskuryakov 2017-01-03 16:14:34 PST
This crashed in IndexedDB code, so it's definitely caused by a preceding test.

The crash looks like a semi-recent regression. Ryan, do you know if we are tracking it in any other bug?

Thread 39 Crashed:: IndexedDatabase Server
0   com.apple.WebCore             	0x0000000104c15523 WTF::CrossThreadQueue<WTF::CrossThreadTask>::tryGetMessage() + 51 (memory:2648)
1   com.apple.WebCore             	0x0000000105835d8c WebCore::IDBServer::UniqueIDBDatabase::executeNextDatabaseTask() + 28 (atomic:927)
2   com.apple.WebCore             	0x0000000104c42589 WebCore::IDBServer::IDBServer::databaseRunLoop() + 73 (memory:2656)
3   com.apple.WebCore             	0x0000000104c41069 WebCore::IDBServer::IDBServer::databaseThreadEntry(void*) + 9
4   com.apple.JavaScriptCore      	0x0000000103483002 WTF::threadEntryPoint(void*) + 178 (functional:1742)
5   com.apple.JavaScriptCore      	0x00000001034833cf WTF::wtfThreadEntryPoint(void*) + 15 (memory:2657)
6   libsystem_pthread.dylib       	0x00007fff8dafd99d _pthread_body + 131
7   libsystem_pthread.dylib       	0x00007fff8dafd91a _pthread_start + 168
8   libsystem_pthread.dylib       	0x00007fff8dafb351 thread_start + 13
Comment 3 Alexey Proskuryakov 2017-01-03 16:15:29 PST
It looks like bug 161414, but I'm not entirely sure if that's the whole story.