jif 6f5dd7b422 Use controlled time for remote initialization timeout test (#29329) ...

## Summary

The remote-control initialization timeout test used a 50 ms wall-clock
deadline around a 10 ms transport timeout. A busy CI runner could miss
that outer deadline even when the rollback behavior was correct.

Pause Tokio time and advance it explicitly through the transport timeout
instead. The test still verifies that initialization fails and emits the
matching connection-closed event, without depending on scheduler speed.

6f5dd7b422 · 2026-06-21 14:53:16 +02:00

History

..

src

Use controlled time for remote initialization timeout test (#29329)

2026-06-21 14:53:16 +02:00

BUILD.bazel

app-server: move transport into dedicated crate (#20545)

2026-05-01 09:23:47 -07:00

Cargo.toml

Use controlled time for remote initialization timeout test (#29329)

2026-06-21 14:53:16 +02:00