Your message dated Sat, 7 Jan 2023 17:21:58 +0000
with message-id <e3ddf749-680b-f2db-32fc-323ef7245...@debian.org>
and subject line RE: FTBFS
has caused the Debian Bug report #1020915,
regarding rust-xmlparser: FTBFS: cdata_err_01 test fails
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 ow...@bugs.debian.org
immediately.)
--
1020915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-xmlparser
Version: 0.13.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
rust-xmlparser/experimental (but not the version in sid) recently
started to FTBFS (previous rebuilds in February and May succeeded):
...
Running
`/build/rust-xmlparser-0.13.3/target/x86_64-unknown-linux-gnu/debug/deps/cdata-4167abb68ff53f68`
running 10 tests
test cdata_05 ... ok
test cdata_08 ... ok
test cdata_01 ... ok
test cdata_02 ... ok
test cdata_03 ... ok
test cdata_04 ... ok
test cdata_09 ... ok
test cdata_06 ... ok
test cdata_07 ... ok
test cdata_err_01 ... FAILED
failures:
---- cdata_err_01 stdout ----
thread 'cdata_err_01' panicked at 'assertion failed: `(left == right)`
left: `Error("invalid CDATA at 1:4 cause a non-XML character '\\0' found at
1:13")`,
right: `Error("invalid CDATA at 1:4 cause a non-XML character '\\u{0}' found
at 1:13")`', tests/cdata.rs:72:1
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.61.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:143:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:182:5
4: cdata::cdata_err_01
at /usr/share/cargo/registry/xmlparser-0.13.3/tests/token.rs:49:17
5: cdata::cdata_err_01::{{closure}}
at /usr/share/cargo/registry/xmlparser-0.13.3/tests/token.rs:45:9
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
cdata_err_01
test result: FAILED. 9 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.01s
error: test failed, to rerun pass '--test cdata'
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code
101
make[1]: *** [debian/rules:6: override_dh_auto_test] Error 25
Andreas
rust-xmlparser_0.13.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
I just did a quick rebuild of 0.13.5. To me it looks like the bug is fixed
Agreed, 0.13.5-1 built on all release architectures when it was uploaded to
unstable (some time after this bug was filed) and also looks fine on
reproducible builds. So i'm going to close this bug.
--- End Message ---
