[Webkit-unassigned] [Bug 221129] New: Flaky JSC test: stress/shared-array-buffer-sort-while-different-thread-is-modifying.js.default

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 29 06:30:13 PST 2021


https://bugs.webkit.org/show_bug.cgi?id=221129

            Bug ID: 221129
           Summary: Flaky JSC test:
                    stress/shared-array-buffer-sort-while-different-thread
                    -is-modifying.js.default
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcatanzaro at gnome.org

JSC stress test is flaky on Red Hat's internal CI (which runs with JIT disabled and cloop enabled). The first known failure was Dec 13. I didn't report it until now because until earlier this week, all the failures occurred on ppc64le, so I incorrectly assumed the issue was specific to that architecture. But the test has since failed on both s390x and x86_64 as well, so it's a more general problem.

Unfortunately, the error message is pretty generic:

Running stress/shared-array-buffer-sort-while-different-thread-is-modifying.js.default
stress/shared-array-buffer-sort-while-different-thread-is-modifying.js.default: Exception: JavaScript execution terminated.
stress/shared-array-buffer-sort-while-different-thread-is-modifying.js.default: ERROR: Unexpected exit code: 1
FAIL: stress/shared-array-buffer-sort-while-different-thread-is-modifying.js.default

I don't know what to make of "JavaScript execution terminated," but it's this same error on all architectures.

Based on the failure history, it might be due to some change that landed in trunk during early December:

Dec 13: failed on ppc64le
Jan 5: failed on ppc64le
Jan 8: failed on ppc64le
Jan 19: failed on ppc64le
Jan 26: failed on s390x
Jan 29: failed on s390x and x86_64

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210129/c394414d/attachment.htm>


More information about the webkit-unassigned mailing list