plugwash

No, I simply ran into the test failure while working on Debian rust packaging.

My searching indicates that the wayland-backend crate is likely affected by "silent behaviour changes" in rustix's event APIs. > When a &mut Vec is passed to [rustix::event::epoll::wait](https://docs.rs/rustix/1/rustix/event/epoll/fn.wait.html), [rustix::event::kqueue::kevent](https://docs.rs/rustix/1/x86_64-unknown-freebsd/rustix/event/kqueue/fn.kevent.html), or [rustix::event::port::getn](https://docs.rs/rustix/1/x86_64-unknown-illumos/rustix/event/port/fn.getn.html),...

The problem seems to be specifically with the "negative NaN" testcases.

I'm not a riscv64 expert, but I wrote a simple test program and ran it on riscv64. use std::str::FromStr; fn main() { println!("{:#066b}",f64::from(f64::from_str("-NaN").unwrap() as f32).to_bits()); println!("{:#034b}",(f64::from_str("-NaN").unwrap() as f32).to_bits()); println!("{:#066b}",f64::from_str("-NaN").unwrap().to_bits()); }...

stack backtrace: 0: __rustc::rust_begin_unwind at /usr/src/rustc-1.90.0/library/std/src/panicking.rs:697:5 1: core::panicking::panic_fmt at /usr/src/rustc-1.90.0/library/core/src/panicking.rs:75:14 2: core::panicking::panic at /usr/src/rustc-1.90.0/library/core/src/panicking.rs:145:5 3: tracing_subscriber::fmt::time::chrono_crate::tests::test_chrono_format_time_utc_default at ./src/fmt/time/chrono_crate.rs:137:9 4: tracing_subscriber::fmt::time::chrono_crate::tests::test_chrono_format_time_utc_default::{{closure}} at ./src/fmt/time/chrono_crate.rs:132:45 5: core::ops::function::FnOnce::call_once at /usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5 6: core::ops::function::FnOnce::call_once at /usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5...