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
More fixes for x86_64-unknown-linux-gnux32
This update libc (all libc testing are passing) and fixes NR_GETRANDOM.
Fix all but one run-pass test (lto-unwind.rs, see rust-lang#45416)
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?
As can see here, the are failing tests for x86_64-unknown-linux-gnux32
run-pass:
lto-unwind.rs
backtrace-debuginfo.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #45652)backtrace.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #45652)command-before-exec.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #45652)command-exec.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #45652)out-of-stack.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #45652)stack-probes-lto.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #45652)stack-probes.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #45652)wait-forked-but-failed-child.rs
(Fixed by More fixes for x86_64-unknown-linux-gnux32 #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
andSO_RCVTIMEO
.Edit 1: update to include #45652 fixes
The text was updated successfully, but these errors were encountered: