Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: b71f2fd0d5382e0b1e4e12e8d522632c11a397d6
https://github.com/WebKit/WebKit/commit/b71f2fd0d5382e0b1e4e12e8d522632c11a397d6
Author: Aakash Jain <[email protected]>
Date: 2025-12-01 (Mon, 01 Dec 2025)
Changed paths:
M Tools/CISupport/ews-build/steps.py
Log Message:
-----------
[EWS] buildbot master unexpectedly stopped and builds failed with error -
Master Shutdown
https://bugs.webkit.org/show_bug.cgi?id=303324
rdar://163674424
Reviewed by Alexey Proskuryakov.
buildbot was abruptly stopping when a JSC test run resulted in 100,000+ test
failures. The reason for that was:
- These test failures generated huge list of failed tests (just the list text
being over 8 MB).
- These failures were parsed and stored as build property twice
(jsc_stress_test_failures and jsc_stress_test_failures_filtered)
- That caused build properties to be over 16 MB.
- After the jscore-tests step was complete, the build-master sent websocket
message containing these build properties
to crossbar (in order to sync to other master).
- This websocket message was over 16MB, which was the already very high limit
we set for crossbar message size.
- crossbar saw WebSocket message exceeding the liit and dropped the connection
to buildbot
- buildbot saw that the connection to crossbar was dropped, didn't know how to
recover, and shut itself down, causing
all the builds to stop.
Fixing the issue by preventing these build properties from being huge.
* Tools/CISupport/ews-build/steps.py:
(RunJavaScriptCoreTests):
(RunJavaScriptCoreTests.run):
Canonical link: https://commits.webkit.org/303694@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications