espresso fails to build with Python 3.13.0b1. For some reason, some tests timed out - not sure if this is Python related, though. The following tests FAILED: 34 - accumulator_correlator (Timeout) 64 - rigid_bond (Timeout) 66 - rotational_inertia (Timeout) 76 - constant_pH_stats (Timeout) 101 - integrator_npt_stats (Timeout) 116 - dpd_stats (Timeout) 124 - collision_detection (Timeout) 151 - thermostats_anisotropic (Timeout) 172 - lb_momentum_conservation (Timeout) https://docs.python.org/3.13/whatsnew/3.13.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.13-b1/fedora-rawhide-x86_64/07530400-espresso/ For all our attempts to build espresso with Python 3.13, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.13-b1/package/espresso/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.13: https://copr.fedorainfracloud.org/coprs/g/python/python3.13-b1/ Let us know here if you have any questions. Python 3.13 is planned to be included in Fedora 41. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
The timeouts happen in a small number of tests which are know to slow down considerably when the host machine is using all of its CPUs. Therefore, these tests are more likely to time out during mass rebuilds. These tests are not strictly essential and can be disabled. I have submitted a new release, espresso-4.2.2-2.fc41, which skips these flaky tests: https://src.fedoraproject.org/rpms/espresso/c/aeb0e8a48820b5357ba691b5ec5cc59ffd73b332?branch=rawhide The build log doesn't suggest there is anything wrong with Python 3.13, so no further action seems required beyond triggering a rebuild with the new release.