• Bug#1101041: rust-pcre2: FTBFS on armel: test result: FAILED. 18 passed

    From Sebastian Ramacher@21:1/5 to All on Sat Mar 22 12:20:01 2025
    Source: rust-pcre2
    Version: 0.2.6-1
    Severity: serious
    Tags: ftbfs
    Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: [email protected]

    Dear maintainer,

    rust-pcre2 fails to build on armel:

    https://buildd.debian.org/status/fetch.php?pkg=rust-pcre2&arch=armel&ver=0.2.6-1%2Bb2&stamp=1742602985&raw=0

    test bytes::tests::find_start_end_and_as_bytes ... FAILED
    test bytes::tests::find_utf_emoji_as_bytes ... FAILED

    failures:

    ---- bytes::tests::find_start_end_and_as_bytes stdout ----

    thread 'bytes::tests::find_start_end_and_as_bytes' panicked at src/bytes.rs:1348:14:
    called `Result::unwrap()` on an `Err` value: Error { kind: JIT, code: -45, offset: None, message: "bad JIT option" }
    stack backtrace:
    0: rust_begin_unwind
    at /usr/src/rustc-1.85.0/library/std/src/panicking.rs:692:5
    1: core::panicking::panic_fmt
    at /usr/src/rustc-1.85.0/library/core/src/panicking.rs:75:14
    2: core::result::unwrap_failed
    at /usr/src/rustc-1.85.0/library/core/src/result.rs:1704:5
    3: core::result::Result<T,E>::unwrap
    at /usr/src/rustc-1.85.0/library/core/src/result.rs:1109:23
    4: pcre2::bytes::tests::find_start_end_and_as_bytes
    at /usr/share/cargo/registry/pcre2-0.2.6/src/bytes.rs:1343:18
    5: pcre2::bytes::tests::find_start_end_and_as_bytes::{{closure}}
    at /usr/share/cargo/registry/pcre2-0.2.6/src/bytes.rs:1334:37
    6: core::ops::function::FnOnce::call_once
    at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
    7: core::ops::function::FnOnce::call_once
    at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

    ---- bytes::tests::find_utf_emoji_as_bytes stdout ----

    thread 'bytes::tests::find_utf_emoji_as_bytes' panicked at src/bytes.rs:1369:14:
    called `Result::unwrap()` on an `Err` value: Error { kind: JIT, code: -45, offset: None, message: "bad JIT option" }
    stack backtrace:
    0: rust_begin_unwind
    at /usr/src/rustc-1.85.0/library/std/src/panicking.rs:692:5
    1: core::panicking::panic_fmt
    at /usr/src/rustc-1.85.0/library/core/src/panicking.rs:75:14
    2: core::result::unwrap_failed
    at /usr/src/rustc-1.85.0/library/core/src/result.rs:1704:5
    3: core::result::Result<T,E>::unwrap
    at /usr/src/rustc-1.85.0/library/core/src/result.rs:1109:23
    4: pcre2::bytes::tests::find_utf_emoji_as_bytes
    at /usr/share/cargo/registry/pcre2-0.2.6/src/bytes.rs:1364:18
    5: pcre2::bytes::tests::find_utf_emoji_as_bytes::{{closure}}
    at /usr/share/cargo/registry/pcre2-0.2.6/src/bytes.rs:1356:33
    6: core::ops::function::FnOnce::call_once
    at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
    7: core::ops::function::FnOnce::call_once
    at /usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.


    failures:
    bytes::tests::find_start_end_and_as_bytes
    bytes::tests::find_utf_emoji_as_bytes

    test result: FAILED. 18 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.15s

    error: test failed, to rerun pass `--lib`
    dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101

    Cheers
    --
    Sebastian Ramacher

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat Mar 22 21:00:02 2025
    This is a multi-part message in MIME format...

    Your message dated Sat, 22 Mar 2025 19:50:35 +0000
    with message-id <[email protected]>
    and subject line Bug#1101041: fixed in rust-pcre2 0.2.9-1
    has caused the Debian Bug report #1101041,
    regarding rust-pcre2: FTBFS on armel: test result: FAILED. 18 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.15s
    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 [email protected]
    immediately.)


    --
    1101041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101041
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 22 Mar 2025 11:12:00 +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=-105.5 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
    DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
    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, 9; hammy, 150; neutral, 85; 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: <[email protected]>
    Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:3634