Bug 205724 - Flaky Test: imported/w3c/web-platform-tests/IndexedDB/large-requests-abort.html
Summary: Flaky Test: imported/w3c/web-platform-tests/IndexedDB/large-requests-abort.html
Status: NEW
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
URL:
Keywords:
Depends on:
Blocks: 50856
  Show dependency treegraph
 
Reported: 2020-01-03 07:27 PST by WebKit Commit Bot
Modified: 2020-01-03 22:01 PST (History)
2 users (show)

See Also:


Attachments
Archive of layout-test-results from webkit-cq-01 (3.57 MB, application/zip)
2020-01-03 07:27 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 2020-01-03 07:27:28 PST
This is an automatically generated bug from the commit-queue.
imported/w3c/web-platform-tests/IndexedDB/large-requests-abort.html has been flaky on the commit-queue.

imported/w3c/web-platform-tests/IndexedDB/large-requests-abort.html was authored by youennf@gmail.com.
https://trac.webkit.org/browser/trunk/LayoutTests/imported/w3c/web-platform-tests/IndexedDB/large-requests-abort.html

The commit-queue just saw imported/w3c/web-platform-tests/IndexedDB/large-requests-abort.html flake (DumpRenderTree crashed) while processing attachment 386673 [details] on bug 205326.
Bot: webkit-cq-01  Port: <class 'webkitpy.common.config.ports.MacPort'>  Platform: Mac OS X 10.13.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 2020-01-03 07:27:29 PST
Created attachment 386682 [details]
Archive of layout-test-results from webkit-cq-01
Comment 2 Alexey Proskuryakov 2020-01-03 22:01:28 PST
Another memory corruption crash. Probably not actionable, other than by fixing all memory corruption issues in IndexedDB.