Failing tests for x86_64-unknown-linux-gnux32

a783894
Opened by Marco A L Barbosa at 2023-11-20 14:50:11

As can see here, the are failing tests for x86_64-unknown-linux-gnux32

run-pass:

  • lto-unwind.rs
  • backtrace-debuginfo.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)
  • backtrace.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)
  • command-before-exec.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)
  • command-exec.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)
  • out-of-stack.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)
  • stack-probes-lto.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)
  • stack-probes.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)
  • wait-forked-but-failed-child.rs (Fixed by https://github.com/rust-lang/rust/pull/45652)

@alexcrichton suggests that it is a problem with stack walk.

libstd:

  • net::tcp::tests::timeouts
  • net::udp::tests::timeout
  • sys::imp::ext::net::test::timeouts
  • io::cursor::tests::test_box_slice_writer (segfault)

The timeout are related with timeval, setsockopt and SO_RCVTIMEO.

Edit 1: update to include https://github.com/rust-lang/rust/pull/45652 fixes

  1. Triage: Does anyone know the current status of x86_64-unknown-linux-gnux32 tests? The original link is broken and I'm not sure if we run these tests continuously somewhere?

    Martin Nordholts at 2023-11-20 14:50:11