Bug 158646 – [Yosemite Release WK2] imported/w3c/IndexedDB-private-browsing/idbfactory_open9.html is a flaky timeout

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: New Bugs

[Ryan Haddad]

imported/w3c/IndexedDB-private-browsing/idbfactory_open9.html is a flaky timeout

<https://build.webkit.org/builders/Apple%20Yosemite%20Release%20WK2%20(Tests)/builds/15220>

<https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2FIndexedDB-private-browsing%2Fidbfactory_open9.html>

[Ryan Haddad]

Seems to time out alongside imported/w3c/IndexedDB-private-browsing/idbfactory_open9.html

[Ryan Haddad]

(In reply to comment #1)
> Seems to time out alongside
> imported/w3c/IndexedDB-private-browsing/idbfactory_open9.html

By that, I meant imported/blink/storage/indexeddb/blob-delete-objectstore-db.html

[Alexey Proskuryakov]

I wonder if these timeouts are misreported crashes, like in bug 158665.

[Brady Eidson]

(In reply to comment #3)
> I wonder if these timeouts are misreported crashes, like in bug 158665.

I would love a conclusion on that, as some of these IDB timeouts are beyond mysterious - How do we find out for sure?

[Alexey Proskuryakov]

I checked the bot where the build quoted by Ryan took place, and there is no crash stored there that would be relevant. So chances are that it's a true timeout.

Perhaps we could temporarily enable sampling on timeout, or even take a spindump. I'd r+ a patch for that.

[Brady Eidson]

(In reply to comment #5)
> I checked the bot where the build quoted by Ryan took place, and there is no
> crash stored there that would be relevant. So chances are that it's a true
> timeout.
> 
> Perhaps we could temporarily enable sampling on timeout, or even take a
> spindump. I'd r+ a patch for that.

I would r+ one, too, but I certainly don't know how to implement one myself.

[Alexey Proskuryakov]

Whoops, this timeout in particular is not a freeze (at least not in WebKitTestRunner or WebContent). It has output: https://build.webkit.org/results/Apple%20Yosemite%20Release%20WK2%20(Tests)/r201935%20(15220)/imported/w3c/IndexedDB-private-browsing/idbfactory_open9-pretty-diff.html

Enabling sample on WKTR is easy (we'd just need to remove --no-sample from arguments), but this is a Databases process freeze at best, and more likely not a freeze at all.

[Brady Eidson]

(In reply to comment #7)
> Whoops, this timeout in particular is not a freeze (at least not in
> WebKitTestRunner or WebContent). It has output:
> https://build.webkit.org/results/Apple%20Yosemite%20Release%20WK2%20(Tests)/
> r201935%20(15220)/imported/w3c/IndexedDB-private-browsing/idbfactory_open9-
> pretty-diff.html
> 
> Enabling sample on WKTR is easy (we'd just need to remove --no-sample from
> arguments), but this is a Databases process freeze at best, and more likely
> not a freeze at all.

Confirming, this cannot be a database process freeze (or crash, or hang), because this is a private browsing test: Database process is not involved at all.

[Ahmad Saleem]

It seems that we don't have any timeout since I couldn't find any platform specific expectations by looking into 'searchfox.org' on wubkat index with 'IndexedDB-private-browsing/idbfactory_open9' keyword and only results (test and expectation file).

Marking this as 'RESOLVED CONFIGURATION CHANGED'.