Bug 322398 – [EWS] Don't mark the build as exception when extract-test-results is killed on the buildmaster

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

[Aakash Jain]

The extract-test-results EWS step unzips the results archive on the buildmaster. Under disk pressure the unzip can exceed buildbot's 5-minute no-output timeout and then survive SIGKILL, which surfaces as a build exception and an unnecessary retry even though the archive is already uploaded to S3 and the tests have already run.

This recurs on the iOS WPT test queue (e.g. several builds on 2026-08-14, plus 08-05 and 08-07), each time marking an engineer's build as an exception for a purely master-side hiccup.

Fix: treat an extraction failure as a non-fatal step failure instead of a build exception, and include the archive size in the step summary so oversized archives are easy to spot.

[Radar WebKit Bug Importer]

<rdar://problem/185686807>

[Aakash Jain]

Pull request: https://github.com/WebKit/WebKit/pull/72304

[Aakash Jain]

Recent examples, all on the iOS-26-Simulator-WPT-WK2-Tests-EWS queue (extract-test-results ended in EXCEPTION with "SIGKILL failed to kill process", each ~310s = buildbot's 5-minute no-output timeout plus the SIGTERM/SIGKILL grace):

- 2026-08-14: https://ews-build.webkit.org/#/builders/154/builds/43217
- 2026-08-14: https://ews-build.webkit.org/#/builders/154/builds/43208
- 2026-08-07: https://ews-build.webkit.org/#/builders/154/builds/42141
- 2026-08-05: https://ews-build.webkit.org/#/builders/154/builds/41675

The WPT queue produces the largest results archives, so it trips the master-side unzip timeout under disk pressure most often.

[EWS]

Committed 319826@main (09003477a258): <https://commits.webkit.org/319826@main>

Reviewed commits have been landed. Closing PR #72304 and removing active labels.