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
thread '<unnamed>' panicked at 'assertion failed: signal(libc::SIGPIPE, libc::SIG_IGN) != libc::SIG_ERR', libstd/sys/unix/mod.rs:85:9
note: Run with `RUST_BACKTRACE=1`for a backtrace.
error: process didn't exit successfully: `qemu-sparc64 /target/sparc64-unknown-linux-gnu/release/deps/slice_deque-5da7fc08593c2b4e` (signal: 4, SIGILL: illegal instruction)
It doesn't look like cross tests are periodically run against travis (e.g. every 24-h), is that so? If so running the test suite periodically might help discover breakage introduced upstream.
The text was updated successfully, but these errors were encountered:
This doesn't reproduce anymore as of cross 2f24bd4.
Sample code demonstrating it works is as of Rust 1.61.0 stable.
tmp_dir=$(mktemp -d)cd"$tmp_dir"
git clone https://github.com/cross-rs/cross
cd cross
# checkout specific version known to work: latest commit on main tested.
git checkout 2f24bd4a81fcb375bc0acf9d0aa6a80d8f4123a0
cargo build
cd ..
git clone https://github.com/gnzlbg/slice_deque
cd slice_deque
"$tmp_dir"/cross/target/debug/cross test --target sparc64-unknown-linux-gnu
cd~
rm -r "$tmp_dir"
All the tests pass, suggesting the issue has been fixed upstream.
With error (see here):
It doesn't look like cross tests are periodically run against travis (e.g. every 24-h), is that so? If so running the test suite periodically might help discover breakage introduced upstream.
The text was updated successfully, but these errors were encountered: