[INFO] cloning repository https://github.com/chrisj/piston-tests [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/chrisj/piston-tests" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fchrisj%2Fpiston-tests", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fchrisj%2Fpiston-tests'... [INFO] [stderr] error: copy-fd: write returned: No space left on device [INFO] [stderr] fatal: cannot copy '/usr/share/git-core/templates/hooks/pre-rebase.sample' to '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fchrisj%2Fpiston-tests/hooks/pre-rebase.sample': No space left on device [WARN] Retrying crate fetch in 3 seconds (attempt 1) [INFO] cloning repository https://github.com/chrisj/piston-tests [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/chrisj/piston-tests" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fchrisj%2Fpiston-tests", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fchrisj%2Fpiston-tests'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] b0aafc5f8cfe8c75c5f555b0aebe6047494b14f5 [INFO] testing chrisj/piston-tests against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_in_2025-retry-1 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fchrisj%2Fpiston-tests" "/workspace/builds/worker-2-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-2-tc1/source'... [INFO] [stderr] done. [INFO] started tweaking git repo https://github.com/chrisj/piston-tests [INFO] finished tweaking git repo https://github.com/chrisj/piston-tests [INFO] tweaked toml for git repo https://github.com/chrisj/piston-tests written to /workspace/builds/worker-2-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/chrisj/piston-tests on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/chrisj/piston-tests already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * src/main.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] warning: path `src/main.rs` was erroneously implicitly accepted for binary `spinning-square`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded pistoncore-window v0.23.0 [INFO] [stderr] Downloaded libloading v0.3.1 [INFO] [stderr] error: failed to unpack package `libloading v0.3.1` [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] failed to create directory `/workspace/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/libloading-0.3.1` [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No space left on device (os error 28) command failed: exit status: 101 warning: An explicit [[bin]] section is specified in Cargo.toml which currently disables Cargo from automatically inferring other binary targets. This inference behavior will change in the Rust 2018 edition and the following files will be included as a binary target: * src/main.rs This is likely to break cargo build or cargo test as these files may not be ready to be compiled as a binary target today. You can future-proof yourself and disable this warning by adding `autobins = false` to your [package] section. You may also move the files to a location where Cargo would not automatically infer them to be a target, such as in subfolders. For more information on this warning you can consult https://github.com/rust-lang/cargo/issues/5330 warning: path `src/main.rs` was erroneously implicitly accepted for binary `spinning-square`, please set bin.path in Cargo.toml warning: no edition set: defaulting to the 2015 edition while the latest is 2024 Blocking waiting for file lock on package cache Blocking waiting for file lock on package cache Downloading crates ... Downloaded pistoncore-window v0.23.0 Downloaded libloading v0.3.1 error: failed to unpack package `libloading v0.3.1` Caused by: failed to create directory `/workspace/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/libloading-0.3.1` Caused by: No space left on device (os error 28)