Bug 211198 – REGRESSION (r260802-r260858): stress/rest-parameter-many-arguments.js.ftl-no-cjit-small-pool and stress/tailCallForwardArguments.js.ftl-no-cjit-small-pool timing out on JSC debug bot

• Component: JavaScriptCore
• Status: NEW

[Ryan Haddad]

The following two tests are timing out on JSC debug bot:

stress/rest-parameter-many-arguments.js.ftl-no-cjit-small-pool
stress/tailCallForwardArguments.js.ftl-no-cjit-small-pool 

https://build.webkit.org/builders/Apple-Catalina-Debug-JSC-Tests/builds/776/steps/jscore-test/logs/stdio

https://results.webkit.org/?suite=javascriptcore-tests&suite=javascriptcore-tests&test=stress%2Frest-parameter-many-arguments.js.ftl-no-cjit-small-pool&test=stress%2FtailCallForwardArguments.js.ftl-no-cjit-small-pool

[Ryan Haddad]

Because of https://bugs.webkit.org/show_bug.cgi?id=210063, we don't have a lot of test result granularity to sift through.

Here is the regression range:
https://trac.webkit.org/log/webkit/?action=stop_on_copy&mode=stop_on_copy&rev=260858&stop_rev=260839&limit=100&verbose=on

[Ryan Haddad]

(In reply to Ryan Haddad from comment #1)
> Because of https://bugs.webkit.org/show_bug.cgi?id=210063, we don't have a
> lot of test result granularity to sift through.
> 
> Here is the regression range:
> https://trac.webkit.org/log/webkit/
> ?action=stop_on_copy&mode=stop_on_copy&rev=260858&stop_rev=260839&limit=100&v
> erbose=on
This range was starting with the last successful run with no failures, but I don't think I can trust that result (it doesn't look like it ran all the tests?)

Here are the JSC changes between the last run with a verifiable result that didn't exhibit the timeouts and the first one that did:
https://trac.webkit.org/log/webkit/trunk/Source/JavaScriptCore?action=stop_on_copy&mode=stop_on_copy&rev=260858&stop_rev=260803&limit=100&verbose=on

[Radar WebKit Bug Importer]

<rdar://problem/62613847>