Bug 2366198
| Summary: | notmuch fails to build with Python 3.14: T380-atomicity: Testing atomicity: FAIL detected >10 abort points | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Karolina Surma <ksurma> |
| Component: | notmuch | Assignee: | Michael J Gruber <mjg> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | epel-packagers-sig, ksurma, mhroncok, mjg |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-05-14 14:14:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2322407 | ||
|
Description
Karolina Surma
2025-05-14 08:42:40 UTC
T380 sucks for various reasons, such as:
- it outputs the actual result where it should state the expected ("test for ...")
- it can succeed for the wrong reasons (such as gdb missing)
- it creates ugly bash errors when gdb failed to write to the output file
I tried upstreaming patches in 2022 but didn't succeed.
If I remember correctly, it's also prone to timeout issues (like other tests).
In this instance, I would expect "scripting gdb in python" to be broken, and I vaguely remember we had this before. As such it does not indicate a problem with notmuch per se, maybe not even with its test suite.
So, after adding in more test debug, I see: ``` /etc/gdbinit:9: Error in sourced command file: Scripting in the "Python" language is not supported in this copy of GDB. ``` I guess gdb needs to be rebuild with py scripting ... Should I reassign to GDB, close invalid, or just wait? Please try again now - I bootstrapped gdb first without, then with Python, but didn't bump the version, so most probably the one without got pulled to your environment. Now there should be only one gdb version in Copr, and the one with Python. Thanks, that was it. I guess it's not a bug then ;) Ooooch, like that. Yes, the next build of notmuch was successful. Thank you for looking into it. |