You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like all of them fail occasionally but i686-linux-android is pretty bad, with an 11% failure rate per GH's metrics. Some sample messages:
adb: error: failed to copy '/checkout/target/i686-linux-android/debug/deps/cmsg-930d5ec3aabcc80f' to '/data/local/tmp/cmsg-930d5ec3aabcc80f': remote secure_mkdirs failed: Read-only file system
thread 'main' panicked at /tmp/runtest.rs:49:9:
failed to find successful test run
stack backtrace:
status: exit status:127
stdout ---
stderr ---
/system/bin/sh: /data/local/tmp/linux_fcntl-d0799fab8ac010c3: not found
0: std::panicking::begin_panic
at /rustc/e16a049adbf94d610787430b6efdf31d896dc5b6/library/std/src/panicking.rs:767:51:runtest::main
2: core::ops::function::FnOnce::call_once
Activity
tgross35 commentedon Mar 4, 2025
Sample failure on aarch64 https://github.com/rust-lang/libc/actions/runs/13663057122/job/38198631635, timed out with
ci: Disable some of the Android jobs
tgross35 commentedon Jun 2, 2025
This seems to have gotten much worse recently so I'm disabling a couple of the jobs for now in #4470. Possible flakiness with the i686 repos? I don't know why these would be worse on Android than the rest of our Docker tests https://github.com/rust-lang/libc/actions/runs/15312115853/job/43079077383.
ci: Disable the i686 Android job
ci: Disable the i686 Android job
ci: Disable the i686 Android job
ci: Disable the i686 Android job
ci: Disable the i686 Android job