Bug 206869 – Regression: JSC armv7 test failure stress/numberingSystemsForLocale-cached-strings-should-be-immortal-and-safe-for-concurrent-access.js.default

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Tools / Tests

[Aakash Jain]

JSC test stress/numberingSystemsForLocale-cached-strings-should-be-immortal-and-safe-for-concurrent-access.js.default is failing on trunk for last few days.

e.g.: https://ews-build.webkit.org/#/builders/26/builds/7547

[Aakash Jain]

Most probably introduced by r255112 (https://bugs.webkit.org/show_bug.cgi?id=206779

[Mark Lam]

Already fixed in  r255120: <http://trac.webkit.org/r255120>. for https://webkit.org/b/206791.  Note that the jsc-armv7 bot of https://webkit.org/b/206791 is green.

*** This bug has been marked as a duplicate of bug 206791 ***

[Aakash Jain]

(In reply to Mark Lam from comment #2)
> Already fixed in  r255120: <http://trac.webkit.org/r255120>. for https://webkit.org/b/206791.

But the test is still failing. e.g.: https://ews-build.webkit.org/#/builders/26/builds/7542


> Note that the jsc-armv7 bot of https://webkit.org/b/206791 is green.
The green indicates that the patch did not introduce any new failure. If you click on the bubble https://ews-build.webkit.org/#/builders/26/builds/7407 (or look at any recent ARMV7 EWS build) it says: 'Found 1 pre-existing JSC test failure: stress/numberingSystemsForLocale-cached-strings-should-be-immortal-and-safe-for-concurrent-access.js.default'

[Caio Lima]

We are going to investigate this on https://bugs.webkit.org/show_bug.cgi?id=206864. We skipped the test for now.

[Caio Lima]

*** This bug has been marked as a duplicate of bug 206864 ***

[Mark Lam]

(In reply to Aakash Jain from comment #3)
> The green indicates that the patch did not introduce any new failure. If you
> click on the bubble https://ews-build.webkit.org/#/builders/26/builds/7407
> (or look at any recent ARMV7 EWS build) it says: 'Found 1 pre-existing JSC
> test failure:
> stress/numberingSystemsForLocale-cached-strings-should-be-immortal-and-safe-
> for-concurrent-access.js.default'

Thanks for the clarification.  I had forgotten about that.

(In reply to Caio Lima from comment #4)
> We are going to investigate this on
> https://bugs.webkit.org/show_bug.cgi?id=206864. We skipped the test for now.

Skipping is probably the correct remedy for this.  The test creates 100 threads all running concurrently.  This would most likely exhaust the resources on a armv7 machine, and would probably abort / fail a RELEASE_ASSERT when it fails to create the threads.