Bug#922099: rust-ripgrep FTBFS, crlf related tests fail.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#922099: rust-ripgrep FTBFS, crlf related tests fail.

peter green-2
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

Reply | Threaded
Open this post in threaded view
|

Bug#922099: marked as done (rust-ripgrep FTBFS, crlf related tests fail.)

Debian Bug Tracking System
Your message dated Tue, 12 Feb 2019 09:22:24 +0000
with message-id <[hidden email]>
and subject line Bug#922099: fixed in rust-ripgrep 0.10.0-2
has caused the Debian Bug report #922099,
regarding rust-ripgrep FTBFS, crlf related tests fail.
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 [hidden email]
immediately.)


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

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

Source: rust-ripgrep
Source-Version: 0.10.0-2

We believe that the bug you reported is fixed in the latest version of
rust-ripgrep, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [hidden email],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru <[hidden email]> (supplier of updated rust-ripgrep package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [hidden email])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 12 Feb 2019 09:25:39 +0100
Source: rust-ripgrep
Architecture: source
Version: 0.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers <[hidden email]>
Changed-By: Sylvestre Ledru <[hidden email]>
Closes: 921693 922099
Changes:
 rust-ripgrep (0.10.0-2) unstable; urgency=medium
 .
   * Package ripgrep 0.10.0 from crates.io using debcargo 2.2.10
   * Force grep-searcher to be at least >= 0.1.3 to avoid bug #916615
   * Disable Windows specific test (closes: #922099)
     https://github.com/BurntSushi/ripgrep/commit/a4868b88351318182eed3b801d0c97a106a7d38f
 .
   [ Peter Michael Green ]
   * Use a temporary directory under the package build directory
     (avoids issues when multiple people build the package on the same machine)
     (Closes: #921693)
Checksums-Sha1:
 6a4018b768b597ec0606984be3907cc0312a60ba 2570 rust-ripgrep_0.10.0-2.dsc
 be67956d132cab62989194d187bc555423cc4ae2 5412 rust-ripgrep_0.10.0-2.debian.tar.xz
 983254771b4d5de0df5073082861440742f26bfe 10173 rust-ripgrep_0.10.0-2_amd64.buildinfo
Checksums-Sha256:
 9c176bcad270d55344d496009008b9b41d86a533e387203c025a7b8f7c07b3d0 2570 rust-ripgrep_0.10.0-2.dsc
 59afb151e5b8624f6d55cb18e4468eaf0e1fb670d4f2c2aa5c6cd192fb9810fe 5412 rust-ripgrep_0.10.0-2.debian.tar.xz
 ea6fe94c28dfa51dfa7ab77dee7cb199c069aec87d29bdf71c257806ee821d8b 10173 rust-ripgrep_0.10.0-2_amd64.buildinfo
Files:
 fbb793a4f623df4b68648064c2c70579 2570 utils optional rust-ripgrep_0.10.0-2.dsc
 ba2d37f152439c26adbe826c4e6b98a3 5412 utils optional rust-ripgrep_0.10.0-2.debian.tar.xz
 1de8c9fd29322d0c1964c113eff5f01c 10173 utils optional rust-ripgrep_0.10.0-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAlxijFAACgkQfmUo2nUv
G+FTAw/+I/Zt8YP0hwB4a/psr0833VFac7bUevHMXsVDoWV1EvAKwgmfcmWv+7ef
Ry2p7B3w/swz3U7UVMZAA27WFhr1YOsthzc9Wtf1OxdFVaCqoVitijdxyDgqVdVE
FIdHkdAZmmA1b4nrS1pQbInsiLM7raq7z9MMvyJAIqLeP03+yX2wweAXVO+WB71D
mIVeXaFi/ugeoYdmFtRagp+soDsB34pxbdP3XJJnX2zFRij6xCsTi5hjiTlvD6tC
5Ov5a4vVjoU1spF7dUdWvLWcAU6HUDohfikrYXv/rZKXt7xCdr4USA5sptQ88LDH
qSSXPtGsI0l3UCNCrYpnAxg2kN5pyh4jwkZCfXWQf2nPzq6pBSKVt9SR+NGJs/yj
zWf86nGNUT3nBjDg9y5ftz5XcDsSXhxeki4ps8kAdiFCgN8ILp8zqKh8iO9Hlf7G
mMQPdhUNPvEnou9mFsGweDUbm61McHXO9+jc3jw3ah4wzRDlSzMmQLw0tWY+3f1h
b+js4MGzi51Pv/LlP7ebyDVdDwL2zOtNoXNRtETxdpAX+Q/az+hGxWFEwU2mJCwO
EKxF4uLB/o6u75lD418dt33NVvnuKaTGRRlHn/bnnzGPdJ+UszrdnP6+bdbCcug+
9bz/ewwLYtxLPPrulJHdCeyMCeY2+fWeOGw3mdYRm2i5zr2+ncc=
=QXKs
-----END PGP SIGNATURE-----