Bug#1055120: marked as done (rust-chrono breaks rust-pyo3 autopkgtest: panicked at 'called `Option::unwrap()` on a `None` value')

Debian Bug Tracking System Thu, 09 Nov 2023 13:09:19 -0800

Your message dated Thu, 09 Nov 2023 21:04:32 +0000
with message-id <e1r1ccw-00af7z...@fasolo.debian.org>
and subject line Bug#1055120: fixed in rust-pyo3 0.19.2-1
has caused the Debian Bug report #1055120,
regarding rust-chrono breaks rust-pyo3 autopkgtest: panicked at 'called 
`Option::unwrap()` on a `None` value'
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.)


-- 
1055120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

--- Begin Message ---
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:
1099s
1099s ---- 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_unwind
1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s    1: core::panicking::panic_fmt
1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s    2: core::panicking::panic
1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
1099s    3: core::option::Option<T>::unwrap
1099s 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:9
1099s 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:9
1099s 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_once
1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s   10: core::ops::function::FnOnce::call_once
1099s 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_unwind
1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s    1: core::panicking::panic_fmt
1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s    2: core::panicking::panic
1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
1099s    3: core::option::Option<T>::unwrap
1099s 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:9
1099s 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:9
1099s 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_once
1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s   10: core::ops::function::FnOnce::call_once
1099s 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_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_unwind
1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s    1: core::panicking::panic_fmt
1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s    2: core::result::unwrap_failed
1099s at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
1099s    3: core::result::Result<T,E>::unwrap
1099s 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:9
1099s 6: pyo3::conversions::chrono::tests::test_pyo3_datetime_frompyobject::{{closure}}
1099s              at ./src/conversions/chrono.rs:651:17
1099s 7: pyo3::conversions::chrono::tests::test_pyo3_datetime_frompyobject
1099s              at ./src/conversions/chrono.rs:681:9
1099s 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_once
1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s   10: core::ops::function::FnOnce::call_once
1099s 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_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_unwind
1099s at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1099s    1: core::panicking::panic_fmt
1099s at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
1099s    2: core::result::unwrap_failed
1099s at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
1099s    3: core::result::Result<T,E>::unwrap
1099s 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:9
1099s 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:9
1099s 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_once
1099s at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s   10: core::ops::function::FnOnce::call_once
1099s 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

--- End Message ---

--- Begin Message ---

Source: rust-pyo3
Source-Version: 0.19.2-1
Done: Peter Michael Green <plugw...@debian.org>

We believe that the bug you reported is fixed in the latest version of
rust-pyo3, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Michael Green <plugw...@debian.org> (supplier of updated rust-pyo3 
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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Thu, 09 Nov 2023 20:25:29 +0000
Source: rust-pyo3
Architecture: source
Version: 0.19.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 
<pkg-rust-maintain...@alioth-lists.debian.net>
Changed-By: Peter Michael Green <plugw...@debian.org>
Closes: 1055120
Changes:
 rust-pyo3 (0.19.2-1) unstable; urgency=medium
 .
   * Team upload.
   * Package pyo3 0.19.2 from crates.io using debcargo 2.6.0
   * Remove upper limit from indexmap dependency.
   * Add upstream patch to make tests pass with new chrono. (Closes: #1055120)
 .
   [ Jelmer Vernooĳ ]
   * Drop obsolete patch newer-indexmap
   * Update copyright file.
Checksums-Sha1:
 dfe235ebd154a197636a9747082bdf7536143f45 3147 rust-pyo3_0.19.2-1.dsc
 656aa07db46a4a6ea0481ff5955fca1d484a8dbd 418228 rust-pyo3_0.19.2.orig.tar.gz
 b751b70e76dcb08e17ed93699be5e62f0fb5e8b7 5432 rust-pyo3_0.19.2-1.debian.tar.xz
 ee28091263e2141c1297cec59fd2709e3835cff8 12310 
rust-pyo3_0.19.2-1_source.buildinfo
Checksums-Sha256:
 2e0da1dcc29fdf718d8ead74712e851f0593886affe030f89ba5e4822cfe51fb 3147 
rust-pyo3_0.19.2-1.dsc
 e681a6cfdc4adcc93b4d3cf993749a4552018ee0a9b65fc0ccfad74352c72a38 418228 
rust-pyo3_0.19.2.orig.tar.gz
 09c0b138f458eb5eecd9596464ca6876e54d158b08820f12879fac06b34a79e3 5432 
rust-pyo3_0.19.2-1.debian.tar.xz
 4a6e9dc9ef746f23b504f5dd5e9512261fae1001fa3cc9fc35ccd70bfdea257d 12310 
rust-pyo3_0.19.2-1_source.buildinfo
Files:
 925e8c597e7716eade2e83819d7b9c52 3147 rust optional rust-pyo3_0.19.2-1.dsc
 2b748818d00ed94bce812208a503b0c9 418228 rust optional 
rust-pyo3_0.19.2.orig.tar.gz
 ef7298b8896f482cd8c4ca9cc4f82bf4 5432 rust optional 
rust-pyo3_0.19.2-1.debian.tar.xz
 b813db219372e13b098cfe53bd3f480c 12310 rust optional 
rust-pyo3_0.19.2-1_source.buildinfo

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

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmVNQ7cUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvVuBAAlXB/m8q0x2n/vdrBssvy31AN2Jfh
2ZRXkB1WKm1reAZQ2V186OrBrj33hpUIUYj934yWL8AtWrqaADfiJ5UWA5pc748A
eNA+8A22F8gdGw6VVl5FsLpfdIKOB6v6TVRaqrlTTsDZoWgBm5r7Ny6i2cL0Es8b
FgfKSlbpbCoiqUgNOKRdwpkQN/1RqTcEYVrOyoTQa/aYwLZXPFeHcHyDeiMXF7fM
mi+RCNsmA4FoQLIS0T/udiQetnFTHDsxEBarFZHNCuT8SjOr8Isf3j2TaFv1aaYa
rpcfuU2qHleAkqxceV46k0sO4N5t4SLtP0gSA+B5gDHwcSyAWCUQJoPwU6IsQWeT
mwQAqsiUkUmzltitL5Q7MjXtApMsQLHrp8Z0XoTw7hCPa20nlf24MUJjjnZ1sOS7
fEkZu6B4D56b8PA33aXD44ZDrH5lsqpzuCYZpJ/v6OlW0sqx0ItnpTgK/qaOpqAD
YfIu3igM8QG3fvcH0vQYcX7EIhBIO3sBd4F0V9pOILyWMv6mzuz7qL8LxlukefxB
EO0AAtpNo3oPJPQi4I3tDGyy7qloehxQ+mlyo+DtczxakhdLWXVR6SFFDStHCkNO
zyi25yzxnEyj/NNyiZv+cMAJReq3dbMPHOFvh8dkZl2VmP55CTeopyNbXWM8fLkq
1uow+k8D+OkVFcE=
=OVDZ
-----END PGP SIGNATURE-----

--- End Message ---

Bug#1055120: marked as done (rust-chrono breaks rust-pyo3 autopkgtest: panicked at 'called `Option::unwrap()` on a `None` value')

Reply via email to