Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sporadic errors with armhf-gnu CI remote test runs #97669

Open
ehuss opened this issue Jun 3, 2022 · 3 comments
Open

Sporadic errors with armhf-gnu CI remote test runs #97669

ehuss opened this issue Jun 3, 2022 · 3 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason)

Comments

@ehuss
Copy link
Contributor

ehuss commented Jun 3, 2022

The armhf-gnu CI runner has been having sporadic errors while running remote tests. The errors typically look something like:

---- [ui] src/test/ui/modules/mod_dir_implicit.rs stdout ----

error: test run failed!
status: exit status: 101
command: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools-bin/remote-test-client" "run" "0" "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/modules/mod_dir_implicit/a"
--- stdout -------------------------------
uploaded "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/modules/mod_dir_implicit/a", waiting for result
------------------------------------------
--- stderr -------------------------------
thread 'main' panicked at 'client.read_exact(&mut header) failed with Connection reset by peer (os error 104)', src/tools/remote-test-client/src/main.rs:310:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
------------------------------------------

There's not much to go on here, as we can't really see the qemu server side.

I don't see a pattern in which tests are failing, so it could be just a general issue with the qemu setup?

@ehuss ehuss added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Jun 3, 2022
This was referenced Jun 3, 2022
@Noratrieb
Copy link
Member

This happened a lot recently:
#109220 (comment)
#109557 (comment)
#109692 (comment)

@saethlin
Copy link
Member

Another one: #118942 (comment)

@saethlin
Copy link
Member

Another one: #121662 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason)
Projects
None yet
Development

No branches or pull requests

3 participants