- Package:
- src:pymatgen-core
- Source:
- src:pymatgen-core
- Submitter:
- Paul Gevers
- Date:
- 2026-09-24 06:21:02 UTC
- Severity:
- normal
Dear maintainer(s), Your package has an autopkgtest, great. I looked at the results of the autopkgtest of your package. I noticed that it regularly fails due to times out due to autopkgtest. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report, but I didn't check if it always hang in the same test. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. Also tests that time out are bad for our infrastructure. I have added your package to our reject_list and will remove it once this bug is closed. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html https://ci.debian.net/packages/p/pymatgen-core/testing/amd64/75123170/ 6634s [gw1] [ 99%] PASSED tests/io/test_babel.py::TestBabelMolAdaptor::test_rotor_search_wrs 7930s tests/io/test_babel.py::TestBabelMolAdaptor::test_rotor_search_srs 7930s [gw1] [ 99%] PASSED tests/io/test_babel.py::TestBabelMolAdaptor::test_rotor_search_srs 10157s tests/io/test_babel.py::TestBabelMolAdaptor::test_rotor_search_rrs autopkgtest [12:28:56]: ERROR: timed out ...
The situation is as you report: pymatgen tests are sometimes flaky. We may have to just skip test_rotor_search_rrs but I'll check if upstream knows how to improve the test first.
Hi Paul, upstream made its next release, which I've uploaded. Would it be possible to run a round of tests on pymatgen-core 2026.8.30+dfsg1-1 to verify that the test flakiness has persisted in the new version? Upstream will want to know if we tested the latest release when I file a bug with them about the issue. Cheers, Drew
Hi Drew, I ran 5 tests on ppc64el and armhf each first (as the queue was empty there), they finished in 10-20 minutes on armhf and ~50 minutes on ppc64el. Then I realized that most failures were on amd64, so I scheduled 1 test there, that finished in 8 minutes. As things are flaky, I then scheduled some more tests and when I went to bed, they were still running. In the end these tests passed, but after 2:15 hours (all four). So I'm not convinced the issue is solved, albeit it might not be a hang. Having a passing test sometimes in 8 minutes and sometimes taking more than 10 times as long isn't great. Paul