NEW155092
js/arraybuffer-wrappers.html is a flaky time out
https://bugs.webkit.org/show_bug.cgi?id=155092
Summary js/arraybuffer-wrappers.html is a flaky time out
Alexey Proskuryakov
Reported 2016-03-06 10:01:03 PST
js/arraybuffer-wrappers.html is a new test that times out very frequently (and when it doesn't, it runs fast). https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=js%2Farraybuffer-wrappers.html
Attachments
Keith Miller
Comment 1 2016-03-06 21:30:19 PST
Is the test still flakey? The link appears to be dead and the test doesn't show up on https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html
Keith Miller
Comment 2 2016-03-06 21:33:47 PST
Wait, nevermind. My internet was acting up and the page was not loading properly.
Ryan Haddad
Comment 3 2016-03-07 11:40:27 PST
Alexey Proskuryakov
Comment 4 2016-03-10 22:25:50 PST
Keith, does this look more like a test bug, or a JSC bug?
Keith Miller
Comment 5 2016-03-10 23:35:56 PST
(In reply to comment #4) > Keith, does this look more like a test bug, or a JSC bug? This looks like a JSC bug. I would expect this test to finish in < 20ms and it definitely should not take more than 1s.
Radar WebKit Bug Importer
Comment 6 2016-03-12 17:28:46 PST
Alexey Proskuryakov
Comment 7 2017-08-25 09:51:42 PDT
*** Bug 155043 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 8 2017-08-25 09:55:13 PDT
Still happening very frequently (also on iOS and Gtk, where we don't have the expectation yet). Keith, would you mind taking a look?
Matt Lewis
Comment 9 2017-09-06 11:28:05 PDT
Marked this test as flaky on iOS for now: https://trac.webkit.org/changeset/221687/webkit
Keith Miller
Comment 10 2017-09-06 11:39:01 PDT
(In reply to Alexey Proskuryakov from comment #8) > Still happening very frequently (also on iOS and Gtk, where we don't have > the expectation yet). > > Keith, would you mind taking a look? Oh, I looked into this a bit. It seems like it's some kind of GC deadlock based on the spindumps on the bots. I'm not sure what causes it or how to reproduce it. I tried running the test (and the 10 tests leading up to it) on all the cores on my machine repeatedly but the issue never reproduced.
Alexey Proskuryakov
Comment 11 2017-09-07 09:26:15 PDT
Is there any instrumentation that can be added to get more information when this happens on the bots?
Keith Miller
Comment 12 2017-09-07 11:11:39 PDT
(In reply to Alexey Proskuryakov from comment #11) > Is there any instrumentation that can be added to get more information when > this happens on the bots? I can't think of anything off the top of my head but maybe @pizlo has some ideas. It's also possible that this isn't a GC deadlock but that's just my current hypothesis.
Note You need to log in before you can comment on or make changes to this bug.