M3.7: robust CLI test deadlines
The --wait end-to-end test hit its 20 s wall-clock deadline under parallel-build load. It now waits on the backend's bufferOpened event and on the process exit through channels, with a generous 120 s limit that a passing run never approaches. The single-instance control tests use a 60 s timeout instead of 10 s. The other CLI tests already wait on the process without a deadline. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
51eba0b3cb
commit
e1638af88a
2 changed files with 28 additions and 16 deletions
|
|
@ -15,7 +15,9 @@ use lutra_control::rendezvous::{self, Instance};
|
|||
use lutra_testkit::EngineBackend;
|
||||
use serde_json::{Value, json};
|
||||
|
||||
const TIMEOUT: Duration = Duration::from_secs(10);
|
||||
/// Generous, because these tests may run beside parallel builds; passing
|
||||
/// runs never wait this long.
|
||||
const TIMEOUT: Duration = Duration::from_secs(60);
|
||||
|
||||
/// Starts a token listener for `backend` and writes its rendezvous file in
|
||||
/// `dir`, as the desktop's claim does.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue