Bug 155091 - storage/indexeddb/modern/exceed-open-file-limit.html is very slow, frequently times out
Summary: storage/indexeddb/modern/exceed-open-file-limit.html is very slow, frequently...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 155041
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-06 09:56 PST by Alexey Proskuryakov
Modified: 2016-03-07 14:40 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2016-03-06 09:56:15 PST
storage/indexeddb/modern/exceed-open-file-limit.html has become very slow, and it frequently times out.

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=storage%2Findexeddb%2Fmodern%2Fexceed-open-file-limit.html

What's curious is that it seems to have regressed when another test got skipped, <https://trac.webkit.org/changeset/197583>.
Comment 1 Brady Eidson 2016-03-06 10:30:10 PST
(In reply to comment #0)
> storage/indexeddb/modern/exceed-open-file-limit.html has become very slow,
> and it frequently times out.
> 
> https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.
> html#showAllRuns=true&tests=storage%2Findexeddb%2Fmodern%2Fexceed-open-file-
> limit.html
> 
> What's curious is that it seems to have regressed when another test got
> skipped, <https://trac.webkit.org/changeset/197583>.

This one and that other one go hand-in-hand. They're basically the same thing - open lots of file handles.

It should just be skipped, too, until we can give *very* slow running tests a chance to finish at the end.
Comment 2 Ryan Haddad 2016-03-07 13:08:20 PST
Skipped with <http://trac.webkit.org/projects/webkit/changeset/197700>
Comment 3 Brady Eidson 2016-03-07 14:40:26 PST
Not a regression in the traditional sense since this was always liable to happen from the moment the test was checked in.

The reason for this timeout is well understood, and is an infrastructure issue. Should not block the umbrella bug.