about summary refs log tree commit diff
path: root/compiler/rustc_mir_transform/src/coverage/mappings.rs
diff options
context:
space:
mode:
authorJacob Pratt <jacob@jhpratt.dev>2024-07-03 03:03:17 -0400
committerGitHub <noreply@github.com>2024-07-03 03:03:17 -0400
commitd8017308725e3d79ece669878eee12534a5725b0 (patch)
tree304812f2f4e372b571a7767f3718e92f7b0def20 /compiler/rustc_mir_transform/src/coverage/mappings.rs
parent24eadb2cf11975c2752203cfa62d4629a394db66 (diff)
parent4b0b97f66ddf36525b844a9c0c775db9f980248f (diff)
downloadrust-d8017308725e3d79ece669878eee12534a5725b0.tar.gz
rust-d8017308725e3d79ece669878eee12534a5725b0.zip
Rollup merge of #127246 - ferrocene:hoverbear/remote-test-client-has-longer-timeout, r=Mark-Simulacrum
Give remote-test-client a longer timeout

In https://github.com/rust-lang/rust/pull/126959, ``@Mark-Simulacrum`` suggested we simply extend the timeout of the `remote-test-client` instead of making it configurable. This is acceptable for my use case.

I'm doing some work with a remote host running tests using `x.py`'s remote test runner system.

After building the `remote-test-server` with:

```bash
./x build src/tools/remote-test-server --target aarch64-unknown-linux-gnu
```

I can transfer the `remote-test-server` to the remote and set up a port forwarded SSH connection, then I run:

```bash
TEST_DEVICE_ADDR=127.0.0.1:12345 ./x.py test library/core --target aarch64-unknown-linux-gnu
```

This works great if the host is nearby, however if the average round trip time is over 100ms (the timeout), it creates problems as it silently trips the timeout.

This PR extends that timeout to a less strict 2s.

r? ``@Mark-Simulacrum``
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/mappings.rs')
0 files changed, 0 insertions, 0 deletions