js/arraybuffer-wrappers.html is a new test that times out very frequently (and when it doesn't, it runs fast).
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
Wait, nevermind. My internet was acting up and the page was not loading properly.
Marked test as flaky in <http://trac.webkit.org/projects/webkit/changeset/197696>
Keith, does this look more like a test bug, or a JSC bug?
(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.
*** Bug 155043 has been marked as a duplicate of this bug. ***
Still happening very frequently (also on iOS and Gtk, where we don't have the expectation yet).
Keith, would you mind taking a look?
Marked this test as flaky on iOS for now:
(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.
Is there any instrumentation that can be added to get more information when this happens on the bots?
(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.