mirror of
https://github.com/openclaw/openclaw.git
synced 2026-10-03 17:53:39 +00:00
83a974025c
* test(macos): wait on signals in the remaining native suites Positive-outcome waits outside the suites #161616 migrated still failed on saturated runners when private 1-5 s deadlines expired before the awaited work ran (StatusMenuSummariesTests:338, GatewayConnectionMediaAuthorityTests:129). Move them onto TestWait: fixture signals, Observation for tracked state, gates and streams, otherwise TestWait.state. Shared owners (TestProcessSupport, AppKit window transitions, Web Chat lifetime) lose their deadlines once, and TestWait gains AsyncTestGate.wait(_:) and TestWait.value(of:_:) so suites stop carrying private copies. Every affected suite declares .testWaitLimit. Bounded absence windows, timeout-subject tests, and producer hold semantics are unchanged. DashboardHTTPFixture's 5 s client bound no longer closes a request a test hook is holding. * test(macos): let Codex shutdown proof wait under the suite limit The force-kill test guarded `client.shutdown()` with a 10 s watchdog. On a saturated runner the watchdog fired first, SIGKILLed the child without reaping it, and the following kill(pid, 0) checks failed (2 of 4 loaded full-suite runs in proof run 36795058911). Production escalates after a 1.5 s graceful wait; the bound was a hang guard, not the subject. Join shutdown under .testWaitLimit instead, killing the children only if the limit cancels the test. * test(macos): order the request timeout before its late send failure The double-resume regression test raced a 10 ms request timeout against a send hook that failed after 100 ms. On a loaded runner the send failure disconnected first and the request failed with the URLError (CI on #162453). The send hook now fails only after the test has observed the timeout. |
||
|---|---|---|
| .. | ||
| .i18n | ||
| android | ||
| ios | ||
| linux | ||
| macos | ||
| macos-mlx-tts | ||
| shared | ||
| swabble | ||