Add test scaffolding for the `remote-test-client` by pvdrz · Pull Request #149071

Add test scaffolding for the `remote-test-client` by pvdrz · Pull Request #149071 · rust-lang/rust

rustbot added A-testsuite

Area: The testsuite used to check the correctness of rustc

S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

T-bootstrap

Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

labels

Nov 19, 2025

pvdrz changed the title ~~Test the remote-test-client timeout~~ Add test scaffolding for the remote-test-client

Nov 19, 2025

pvdrz mentioned this pull request

Nov 19, 2025

bors added S-waiting-on-bors

Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

and removed S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

labels

Nov 20, 2025

Zalathar added a commit to Zalathar/rust that referenced this pull request

Nov 20, 2025

…-timeout-tests, r=jieyouxu

Add test scaffolding for the `remote-test-client`

r? `@jieyouxu`

bors added a commit that referenced this pull request

Nov 20, 2025

Rollup of 10 pull requests

Successful merges:

 - #146925 (Add doc for va_list APIs)
 - #147035 (alloc: fix `Debug` implementation of `ExtractIf`)
 - #147173 (Add support for hexagon-unknown-qurt target)
 - #148261 (rustc_public: Make Id types !Send / !Sync)
 - #148831 (Bump compiler dependencies)
 - #149041 (ignore unsized types in mips64 and sparc64 callconvs)
 - #149056 (fix the fragment_in_dst_padding_gets_overwritten test on s390x)
 - #149071 (Add test scaffolding for the `remote-test-client`)
 - #149095 (rustc-dev-guide subtree update)
 - #149108 ([AIX][ppc64le-linux-gnu] Add Amy Kwan to target maintainers)

r? `@ghost`
`@rustbot` modify labels: rollup

bors added a commit that referenced this pull request

Nov 20, 2025

Rollup of 9 pull requests

Successful merges:

 - #146925 (Add doc for va_list APIs)
 - #147035 (alloc: fix `Debug` implementation of `ExtractIf`)
 - #147173 (Add support for hexagon-unknown-qurt target)
 - #148261 (rustc_public: Make Id types !Send / !Sync)
 - #149041 (ignore unsized types in mips64 and sparc64 callconvs)
 - #149056 (fix the fragment_in_dst_padding_gets_overwritten test on s390x)
 - #149071 (Add test scaffolding for the `remote-test-client`)
 - #149095 (rustc-dev-guide subtree update)
 - #149108 ([AIX][ppc64le-linux-gnu] Add Amy Kwan to target maintainers)

r? `@ghost`
`@rustbot` modify labels: rollup

rust-timer added a commit that referenced this pull request

Nov 20, 2025

Rollup merge of #149071 - ferrocene:pvdrz/remote-test-client-timeout-tests, r=jieyouxu

Add test scaffolding for the `remote-test-client`

r? ``@jieyouxu``

tshepang deleted the pvdrz/remote-test-client-timeout-tests branch

November 20, 2025 19:53

github-actions bot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request

Nov 24, 2025

matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request

Nov 28, 2025

…-timeout, r=Enselic

Add a timeout to the `remote-test-client` connection

Currently, the `remote-test-client` doesn't have a timeout when connecting to the `remote-test-server`. This means that running tests using it can hang indefinitely which causes issues when running tests on CI, for example.

This PR now sets a default timeout of 5 minutes, meaning that if, for example, `TEST_DEVICE_ADDR=<IP:PORT> ./x test --target riscv64gc-unknown-linux-gnu tests/ui` is run and the `remote-test-server` is not reachable by the client, the client will panic after the timeout is reached.

Additionally, the `TEST_DEVICE_CONNECT_TIMEOUT` env variable can be used to set up the timeout to any value (in seconds).

This PR also wires up a test step for `remote-test-client`, which didn't previously have tool tests run in CI.

Edit: ~~blocked by rust-lang#149071~~

rust-timer added a commit that referenced this pull request

Nov 28, 2025

Rollup merge of #147952 - ferrocene:pvdrz/remote-test-client-timeout, r=Enselic

Add a timeout to the `remote-test-client` connection

Currently, the `remote-test-client` doesn't have a timeout when connecting to the `remote-test-server`. This means that running tests using it can hang indefinitely which causes issues when running tests on CI, for example.

This PR now sets a default timeout of 5 minutes, meaning that if, for example, `TEST_DEVICE_ADDR=<IP:PORT> ./x test --target riscv64gc-unknown-linux-gnu tests/ui` is run and the `remote-test-server` is not reachable by the client, the client will panic after the timeout is reached.

Additionally, the `TEST_DEVICE_CONNECT_TIMEOUT` env variable can be used to set up the timeout to any value (in seconds).

This PR also wires up a test step for `remote-test-client`, which didn't previously have tool tests run in CI.

Edit: ~~blocked by #149071~~

github-actions bot pushed a commit to rust-lang/miri that referenced this pull request

Nov 29, 2025

… r=Enselic

Add a timeout to the `remote-test-client` connection

Currently, the `remote-test-client` doesn't have a timeout when connecting to the `remote-test-server`. This means that running tests using it can hang indefinitely which causes issues when running tests on CI, for example.

This PR now sets a default timeout of 5 minutes, meaning that if, for example, `TEST_DEVICE_ADDR=<IP:PORT> ./x test --target riscv64gc-unknown-linux-gnu tests/ui` is run and the `remote-test-server` is not reachable by the client, the client will panic after the timeout is reached.

Additionally, the `TEST_DEVICE_CONNECT_TIMEOUT` env variable can be used to set up the timeout to any value (in seconds).

This PR also wires up a test step for `remote-test-client`, which didn't previously have tool tests run in CI.

Edit: ~~blocked by rust-lang/rust#149071~~

github-actions bot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request

Dec 1, 2025

… r=Enselic

Add a timeout to the `remote-test-client` connection

Currently, the `remote-test-client` doesn't have a timeout when connecting to the `remote-test-server`. This means that running tests using it can hang indefinitely which causes issues when running tests on CI, for example.

This PR now sets a default timeout of 5 minutes, meaning that if, for example, `TEST_DEVICE_ADDR=<IP:PORT> ./x test --target riscv64gc-unknown-linux-gnu tests/ui` is run and the `remote-test-server` is not reachable by the client, the client will panic after the timeout is reached.

Additionally, the `TEST_DEVICE_CONNECT_TIMEOUT` env variable can be used to set up the timeout to any value (in seconds).

This PR also wires up a test step for `remote-test-client`, which didn't previously have tool tests run in CI.

Edit: ~~blocked by rust-lang/rust#149071~~

makai410 pushed a commit to makai410/rustc_public that referenced this pull request

Dec 10, 2025

makai410 pushed a commit to makai410/rust that referenced this pull request

Dec 10, 2025

…-timeout-tests, r=jieyouxu

Add test scaffolding for the `remote-test-client`

r? ``@jieyouxu``

makai410 pushed a commit to makai410/rust that referenced this pull request

Dec 10, 2025

github-actions bot pushed a commit to rust-lang/stdarch that referenced this pull request

Jan 1, 2026

github-actions bot pushed a commit to model-checking/verify-rust-std that referenced this pull request

Jan 17, 2026