RESOLVED FIXED269318
JSC test timeout should never exceed the buildbot timeout 
https://bugs.webkit.org/show_bug.cgi?id=269318
Summary JSC test timeout should never exceed the buildbot timeout
Angelos Oikonomopoulos
Reported 2024-02-13 13:36:06 PST
Currently, run-jsc-stress-tests scales up JSC_timeout by the number of cores. On high core count machines, this pushes the value above the 1200 seconds after which buildbot will kill the running command if it hasn't seen any output. This means that when a single JSC stress test hangs, the whole test run ends up wasted and the user only gets a cryptic command timed out: 1200 seconds without output running message that gives no information as to which test got stuck.
Attachments
Add attachment proposed patch, testcase, etc.
Angelos Oikonomopoulos
Comment 1 2024-02-13 13:41:44 PST
Pull request: https://github.com/WebKit/WebKit/pull/24367
EWS
Comment 2 2024-02-14 02:57:04 PST
Committed 274620@main (36543ae6e0e9): <https://commits.webkit.org/274620@main> Reviewed commits have been landed. Closing PR #24367 and removing active labels.
Radar WebKit Bug Importer
Comment 3 2024-02-14 02:58:13 PST
<rdar://problem/122939729>
Note You need to log in before you can comment on or make changes to this bug.