RESOLVED FIXED302827
[WKCI] filter-test-logs can cause that buildbot ends killing an in-progress step because of no output for more than X seconds 
https://bugs.webkit.org/show_bug.cgi?id=302827
Summary [WKCI] filter-test-logs can cause that buildbot ends killing an in-progress s...
Carlos Alberto Lopez Perez
Reported 2025-11-19 16:20:13 PST
The python script filter-test-logs that we use to send the logs directly to S3 instead of letting buildbot process them can cause that a step times out because of "command timed out: XXX seconds without output running YYY" This has been seen, for example at https://build.webkit.org/#/builders/1618/builds/2542 where a layout test runner was working (very slow, with only 1 CPU assigned, but working). The step couldn't finish before the 3H deadline and because of the filtering no output was printed to stdout before that 3H deadline so buildbot ends killing it
Attachments
Add attachment proposed patch, testcase, etc.
Carlos Alberto Lopez Perez
Comment 1 2025-11-19 16:30:59 PST
Pull request: https://github.com/WebKit/WebKit/pull/54218
EWS
Comment 2 2025-11-20 02:44:34 PST
Committed 303319@main (4f8fc62a1b48): <https://commits.webkit.org/303319@main> Reviewed commits have been landed. Closing PR #54218 and removing active labels.
Radar WebKit Bug Importer
Comment 3 2025-11-20 02:45:15 PST
<rdar://problem/165119555>
Note You need to log in before you can comment on or make changes to this bug.