155092 2016-03-06 10:01:03 -0800 js/arraybuffer-wrappers.html is a flaky time out 2017-09-07 11:11:39 -0700 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 1 ap webkit-unassigned fpizlo ggaren jlewis3 keith_miller ryanhaddad webkit-bug-importer oldest_to_newest 1171430 0 ap 2016-03-06 10:01:03 -0800 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 1171518 1 keith_miller 2016-03-06 21:30:19 -0800 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 1171519 2 keith_miller 2016-03-06 21:33:47 -0800 Wait, nevermind. My internet was acting up and the page was not loading properly. 1171687 3 ryanhaddad 2016-03-07 11:40:27 -0800 Marked test as flaky in <http://trac.webkit.org/projects/webkit/changeset/197696> 1173608 4 ap 2016-03-10 22:25:50 -0800 Keith, does this look more like a test bug, or a JSC bug? 1173624 5 keith_miller 2016-03-10 23:35:56 -0800 (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. 1174109 6 webkit-bug-importer 2016-03-12 17:28:46 -0800 <rdar://problem/25130361> 1342422 7 ap 2017-08-25 09:51:42 -0700 *** Bug 155043 has been marked as a duplicate of this bug. *** 1342424 8 ap 2017-08-25 09:55:13 -0700 Still happening very frequently (also on iOS and Gtk, where we don't have the expectation yet). Keith, would you mind taking a look? 1346019 9 jlewis3 2017-09-06 11:28:05 -0700 Marked this test as flaky on iOS for now: https://trac.webkit.org/changeset/221687/webkit 1346023 10 keith_miller 2017-09-06 11:39:01 -0700 (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. 1346348 11 ap 2017-09-07 09:26:15 -0700 Is there any instrumentation that can be added to get more information when this happens on the bots? 1346431 12 keith_miller 2017-09-07 11:11:39 -0700 (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.