Bug 183266

Summary: stress/ftl-put-by-id-setter-exception-interesting-live-state.js.no-cjit-collect-continuously is a flaky failure
Product: WebKit Reporter: Saam Barati <saam>
Component: JavaScriptCoreAssignee: Tadeu Zagallo <tzagallo>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, benjamin, fpizlo, ggaren, gskachkov, jfbastien, keith_miller, mark.lam, msaboff, rmorisset, ryanhaddad, ticaiolima, webkit-bug-importer, ysuzuki
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=197378
https://bugs.webkit.org/show_bug.cgi?id=201986

Saam Barati
Reported 2018-03-01 15:21:17 PST
...
Attachments
Radar WebKit Bug Importer
Comment 1 2018-03-01 15:21:50 PST
Alexey Proskuryakov
Comment 2 2018-03-25 12:10:39 PDT
There is no crash log on the bot, looks like the test aborts the process without crashing. Running stress/ftl-put-by-id-slow-exception-no-catch.js.no-cjit-collect-continuously stress/ftl-put-by-id-setter-exception-interesting-live-state.js.no-cjit-collect-continuously: Exception: Error42 Running stress/ftl-put-by-id-slow-exception-no-catch.js.dfg-eager Running stress/ftl-put-by-id-slow-exception-no-catch.js.dfg-eager-no-cjit-validate stress/ftl-put-by-id-setter-exception-interesting-live-state.js.no-cjit-collect-continuously: ERROR: Unexpected exit code: 3 FAIL: stress/ftl-put-by-id-setter-exception-interesting-live-state.js.no-cjit-collect-continuously
Yusuke Suzuki
Comment 4 2019-06-14 13:56:34 PDT
(In reply to Ryan Haddad from comment #3) > Still happening > > https://build.webkit.org/builders/ > Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/9804 Now, I'm thinking that this is https://bugs.webkit.org/show_bug.cgi?id=197378 :)
Ryan Haddad
Comment 5 2019-08-15 14:00:06 PDT
This test is still a flaky failure: https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10580/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10583/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10586/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10587/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10595/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10600/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10606/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10608/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10612/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10616/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10620/steps/jscore-test/logs/stdio Not sure if it is related, but stress/ftl-put-by-id-setter-exception.js is also flaky: https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10619/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10577/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10574/steps/jscore-test/logs/stdio https://build.webkit.org/builders/Apple%20High%20Sierra%20Release%20JSC%20%28Tests%29/builds/10602/steps/jscore-test/logs/stdio
Tadeu Zagallo
Comment 6 2019-09-22 11:39:33 PDT
I tested it with a few hundred runs after r250184 and it seems like it doesn't reproduce anymore. *** This bug has been marked as a duplicate of bug 201986 ***
Note You need to log in before you can comment on or make changes to this bug.