Source: rust-chrono, rust-pyo3 Control: found -1 rust-chrono/0.4.31-1 Control: found -1 rust-pyo3/0.19.0-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: breaks needs-update
Dear maintainer(s),With a recent upload of rust-chrono the autopkgtest of rust-pyo3 fails in testing when that autopkgtest is run with the binary packages of rust-chrono from unstable. It passes when run with only packages from testing. In tabular form:
pass fail
rust-chrono from testing 0.4.31-1
rust-pyo3 from testing 0.19.0-3
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of rust-chrono to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rust-chrono https://ci.debian.net/data/autopkgtest/testing/armel/r/rust-pyo3/39387157/log.gz 1099s failures: 1099s1099s ---- conversions::chrono::tests::test_pyo3_datetime_topyobject stdout ---- 1099s thread 'conversions::chrono::tests::test_pyo3_datetime_topyobject' panicked at 'called `Option::unwrap()` on a `None` value', src/conversions/chrono.rs:574:26
1099s stack backtrace: 1099s 0: rust_begin_unwind1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s 1: core::panicking::panic_fmt1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s 2: core::panicking::panic1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
1099s 3: core::option::Option<T>::unwrap1099s at /usr/src/rustc-1.70.0/library/core/src/option.rs:950:21 1099s 4: pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}::{{closure}}
1099s at ./src/conversions/chrono.rs:571:36 1099s 5: pyo3::marker::Python::with_gil 1099s at ./src/marker.rs:433:91099s 6: pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:570:17 1099s 7: pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject 1099s at ./src/conversions/chrono.rs:603:91099s 8: pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:567:40 1099s 9: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s 10: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5 1099s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
1099s 1099s ---- conversions::chrono::tests::test_pyo3_time_topyobject stdout ----1099s thread 'conversions::chrono::tests::test_pyo3_time_topyobject' panicked at 'called `Option::unwrap()` on a `None` value', src/conversions/chrono.rs:798:22
1099s stack backtrace: 1099s 0: rust_begin_unwind1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s 1: core::panicking::panic_fmt1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s 2: core::panicking::panic1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
1099s 3: core::option::Option<T>::unwrap1099s at /usr/src/rustc-1.70.0/library/core/src/option.rs:950:21 1099s 4: pyo3::conversions::chrono::tests::test_pyo3_time_topyobject::{{closure}}::{{closure}}
1099s at ./src/conversions/chrono.rs:797:28 1099s 5: pyo3::marker::Python::with_gil 1099s at ./src/marker.rs:433:91099s 6: pyo3::conversions::chrono::tests::test_pyo3_time_topyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:796:13 1099s 7: pyo3::conversions::chrono::tests::test_pyo3_time_topyobject 1099s at ./src/conversions/chrono.rs:822:91099s 8: pyo3::conversions::chrono::tests::test_pyo3_time_topyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:794:36 1099s 9: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s 10: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5 1099s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
1099s1099s ---- conversions::chrono::tests::test_pyo3_datetime_frompyobject stdout ---- 1099s thread 'conversions::chrono::tests::test_pyo3_datetime_frompyobject' panicked at 'called `Result::unwrap()` on an `Err` value: PyErr { type: <class 'ValueError'>, value: ValueError('invalid or out-of-range time'), traceback: None }', src/conversions/chrono.rs:667:76
1099s stack backtrace: 1099s 0: rust_begin_unwind1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s 1: core::panicking::panic_fmt1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s 2: core::result::unwrap_failed1099s at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
1099s 3: core::result::Result<T,E>::unwrap1099s at /usr/src/rustc-1.70.0/library/core/src/result.rs:1089:23 1099s 4: pyo3::conversions::chrono::tests::test_pyo3_datetime_frompyobject::{{closure}}::{{closure}}
1099s at ./src/conversions/chrono.rs:667:54 1099s 5: pyo3::marker::Python::with_gil 1099s at ./src/marker.rs:433:91099s 6: pyo3::conversions::chrono::tests::test_pyo3_datetime_frompyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:651:171099s 7: pyo3::conversions::chrono::tests::test_pyo3_datetime_frompyobject
1099s at ./src/conversions/chrono.rs:681:91099s 8: pyo3::conversions::chrono::tests::test_pyo3_datetime_frompyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:648:42 1099s 9: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s 10: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5 1099s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
1099s1099s ---- conversions::chrono::tests::test_pyo3_time_frompyobject stdout ---- 1099s thread 'conversions::chrono::tests::test_pyo3_time_frompyobject' panicked at 'called `Result::unwrap()` on an `Err` value: PyErr { type: <class 'ValueError'>, value: ValueError('invalid or out-of-range time'), traceback: None }', src/conversions/chrono.rs:840:60
1099s stack backtrace: 1099s 0: rust_begin_unwind1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s 1: core::panicking::panic_fmt1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s 2: core::result::unwrap_failed1099s at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
1099s 3: core::result::Result<T,E>::unwrap1099s at /usr/src/rustc-1.70.0/library/core/src/result.rs:1089:23 1099s 4: pyo3::conversions::chrono::tests::test_pyo3_time_frompyobject::{{closure}}::{{closure}}
1099s at ./src/conversions/chrono.rs:840:42 1099s 5: pyo3::marker::Python::with_gil 1099s at ./src/marker.rs:433:91099s 6: pyo3::conversions::chrono::tests::test_pyo3_time_frompyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:829:13 1099s 7: pyo3::conversions::chrono::tests::test_pyo3_time_frompyobject 1099s at ./src/conversions/chrono.rs:846:91099s 8: pyo3::conversions::chrono::tests::test_pyo3_time_frompyobject::{{closure}}
1099s at ./src/conversions/chrono.rs:827:38 1099s 9: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s 10: core::ops::function::FnOnce::call_once1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5 1099s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
1099s 1099s 1099s failures: 1099s conversions::chrono::tests::test_pyo3_datetime_frompyobject 1099s conversions::chrono::tests::test_pyo3_datetime_topyobject 1099s conversions::chrono::tests::test_pyo3_time_frompyobject 1099s conversions::chrono::tests::test_pyo3_time_topyobject
OpenPGP_signature.asc
Description: OpenPGP digital signature
