On Fri, 18 May 2018 21:22:48 +0530 Pirate Praveen
<prav...@onenetbeyond.org> wrote:
libgit2 0.27 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will be raised
to serious once libgit2 0.27 is uploaded to unstable.
I rebuilt cargo with libgit2 0.27 and got 4 test failures.
failures:
---- dont_require_submodules_are_checked_out stdout ----
running `/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/release/cargo
build -v`
thread 'dont_require_submodules_are_checked_out' panicked at '
Expected: execs
but: exited with signal: 11
--- stdout
--- stderr
', debian/../vendor/hamcrest-0.1.1/src/core.rs:31:13
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::begin_panic
6: std::panicking::begin_panic_fmt
7: hamcrest::core::assert_that
8: git::dont_require_submodules_are_checked_out
9: <F as alloc::boxed::FnBox<A>>::call_box
10: __rust_maybe_catch_panic
---- git_dep_build_cmd stdout ----
running `/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/release/cargo
build`
thread 'git_dep_build_cmd' panicked at '
Expected: execs
but: exited with signal: 11
--- stdout
--- stderr
warning: path
`/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/cit/t20/foo/src/foo.rs`
was erroneously implicitly accepted for binary `foo`,
please set bin.path in Cargo.toml
', debian/../vendor/hamcrest-0.1.1/src/core.rs:31:13
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::begin_panic
6: std::panicking::begin_panic_fmt
7: hamcrest::core::assert_that
8: git::git_dep_build_cmd
9: <F as alloc::boxed::FnBox<A>>::call_box
10: __rust_maybe_catch_panic
---- git_build_cmd_freshness stdout ----
running `/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/release/cargo
build`
thread 'git_build_cmd_freshness' panicked at '
Expected: execs
but: exited with signal: 6
--- stdout
--- stderr
malloc_consolidate(): invalid chunk size
', debian/../vendor/hamcrest-0.1.1/src/core.rs:31:13
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::begin_panic
6: std::panicking::begin_panic_fmt
7: hamcrest::core::assert_that
8: git::git_build_cmd_freshness
9: <F as alloc::boxed::FnBox<A>>::call_box
10: __rust_maybe_catch_panic
failures:
dont_require_submodules_are_checked_out
git_build_cmd_freshness
git_dep_build_cmd
test result: FAILED. 34 passed; 3 failed; 1 ignored; 0 measured; 0
filtered out
