Skip to content

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

Open
@ehuss

Description

@ehuss

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-CIArea: Our Github Actions CIA-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions