See:
https://github.com/BurntSushi/ripgrep/commit/a4868b88351318182eed3b801d0c97a106a7d38f
Le 12/02/2019 à 02:04, peter green a écrit :
Package: rust-ripgrep
Version: 0.10.0-1
Severity: serious
While performing a test build on s390x to see if bug 916615 was
actually fixed I ran into a new error. I then did a test build on
amd64 and was able to reduce the same testsuite failure, so this
doesn't seem to be architecture specific.
---- feature::f416_crlf_only_matching stdout ----
thread 'feature::f416_crlf_only_matching' panicked at '
printed outputs differ!
expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sherlock
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sherlock
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/feature.rs:455:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
1: std::sys_common::backtrace::print
2: std::panicking::default_hook::{{closure}}
3: std::panicking::default_hook
4: std::panicking::rust_panic_with_hook
5: std::panicking::continue_panic_fmt
6: std::panicking::begin_panic_fmt
7: integration::feature::f416_crlf_only_matching::{{closure}}
at tests/feature.rs:455
8: integration::feature::f416_crlf_only_matching
at tests/macros.rs:7
9: integration::feature::f416_crlf_only_matching::{{closure}}
at tests/macros.rs:5
10: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.32.0/src/libcore/ops/function.rs:238
11: <F as alloc::boxed::FnBox<A>>::call_box
12: __rust_maybe_catch_panic
---- json::crlf stdout ----
thread 'json::crlf' panicked at 'assertion failed: `(left == right)`
left: `SubMatch { m: Text { text: "Sherlock\r" }, start: 56, end: 65
}`,
right: `SubMatch { m: Text { text: "Sherlock" }, start: 56, end: 64
}`', tests/json.rs:298:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
1: std::sys_common::backtrace::print
2: std::panicking::default_hook::{{closure}}
3: std::panicking::default_hook
4: std::panicking::rust_panic_with_hook
5: std::panicking::continue_panic_fmt
6: std::panicking::begin_panic_fmt
7: integration::json::crlf::{{closure}}
at tests/json.rs:298
8: integration::json::crlf
at tests/macros.rs:7
9: integration::json::crlf::{{closure}}
at tests/macros.rs:5
10: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.32.0/src/libcore/ops/function.rs:238
11: <F as alloc::boxed::FnBox<A>>::call_box
12: __rust_maybe_catch_panic
failures:
feature::f416_crlf_only_matching
json::crlf
test result: FAILED. 185 passed; 2 failed; 0 ignored; 0 measured; 0
filtered out
_______________________________________________
Pkg-rust-maintainers mailing list
pkg-rust-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
