notmuch fails to build with Python 3.13.0b1. T380-atomicity: Testing atomicity cat: outcount: No such file or directory /builddir/build/BUILD/notmuch-0.38.3-build/notmuch-0.38.3/test/T380-atomicity.sh: line 79: ((: i < : syntax error: operand expected (error token is "< ") PASS "notmuch new" is idempotent under arbitrary aborts FAIL detected >10 abort points test -gt 10 /builddir/build/BUILD/notmuch-0.38.3-build/notmuch-0.38.3/test/test-lib.sh: line 701: test: -gt: unary operator expected 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/07526340-notmuch/ For all our attempts to build notmuch with Python 3.13, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.13-b1/package/notmuch/ 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.
That test output looks weird because the test suite does not initialize a file which it reads later, and if it's read too early it's empty ... Anyways: T380 passes for me locally in mock (i.e. with your py3.13 copr), as does the whole test suite. The notmuch test has a history of failing on loaded infrastructure, especially on copr, while it passes in koji most of the time and locally always. Apparently it passes in github CI, too. I already make sure to serialize and to avoid shortcuts that `notmuch new` would take otherwise. I may need to do this in even more places. So I'm tempted to close this as invalid, but I'll mark it ON_QA first and hope for a pass run - or even maybe some insight on how to stabilize the test suite! [Curiously, I noticed this failure in 2023-11 already, suggested test suite fixes upstream to get a clearer output, but discussion stalled around style questions.]
Built in side-tag now.