Package: rust-rustix
Version: 0.38.37-2
Severity: serious

The autopkgtests for rust-rustix are failing on i386.

1337s ---- backend::vdso::test_vdso stdout ----
1337s
1337s thread 'backend::vdso::test_vdso' panicked at src/backend/linux_raw/vdso.rs:428:28:
1337s called `Option::unwrap()` on a `None` value
1337s stack backtrace:
1337s 0: rust_begin_unwind
1337s at /usr/src/rustc-1.85.0/library/std/src/panicking.rs:692:5
1337s 1: core::panicking::panic_fmt
1337s at /usr/src/rustc-1.85.0/library/core/src/panicking.rs:75:14
1337s 2: core::panicking::panic
1337s at /usr/src/rustc-1.85.0/library/core/src/panicking.rs:145:5
1337s 3: core::option::unwrap_failed
1337s at /usr/src/rustc-1.85.0/library/core/src/option.rs:2015:5 1337s 4: core::option::Option<T>::unwrap
1337s at /usr/src/rustc-1.85.0/library/core/src/option.rs:978:21 1337s 5: rustix::backend::vdso::test_vdso
1337s at ./src/backend/linux_raw/vdso.rs:428:16
1337s 6: rustix::backend::vdso::test_vdso::{{closure}}
1337s at ./src/backend/linux_raw/vdso.rs:427:15
1337s 7: core::ops::function::FnOnce::call_once
1337s at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
1337s 8: core::ops::function::FnOnce::call_once
1337s at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
1337s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
1337s
1337s
1337s failures:
1337s backend::vdso::test_vdso

It looks like the test in question was newly added with the vdso patches.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Tue, 13 May 2025 19:34:04 +0000
with message-id <E1uEvO8-00BQs0-Na@fasolo.debian.org>
and subject line Bug#1105189: fixed in rust-rustix 0.38.37-3
has caused the Debian Bug report #1105189,
regarding rust-rustix - autopkgtest failure on i386.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


--
1105189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105189
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 13 May 2025 03:08:47 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-117.8 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_NONE,
SPF_NONE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,
USER_IN_DKIM_WHITELIST autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 16; hammy, 150; neutral, 30; spammy,
0. spammytokens:
hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <plugwash@debian.org>
Received: from stravinsky.debian