Bug 1541967
| Summary: | test_gdb check fails on x86_64 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tomas Orsava <torsava> | ||||
| Component: | python3 | Assignee: | Victor Stinner <vstinner> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 29 | CC: | bkabrda, cstratak, dmalcolm, lzachar, mhroncok, mplch, pviktori, rkuska, tomspur, torsava, vstinner | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-02-21 11:29:16 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: | 1638798, 1667919 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Tomas Orsava
2018-02-05 10:36:57 UTC
This issue does not appear to be similar to the reported test_gdb failure on PPC: bz#1132488. This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'. test_gdb does not fail with Python 3.7 on x86_64, but so far I do not see what fixed it. Also I can not reproduce this when running the tests on Fedora Rawhide from cpython source on v3.6.4 tag. This happens though in mock and Koji, still investigating. The failures can be reproduced on Fedora 28 from source: ./configure --with-pydebug make 'EXTRA_CFLAGS=-mcet -fcf-protection -O0' make test TESTOPTS='-v test_gdb' The test test_gdb fails only in debug build, and only if built with control flow protection [0] flags `-mcet -fcf-protection` AND optimization `-O0`. [0] https://fedoraproject.org/wiki/Changes/HardeningFlags28 This issue should be reported upstream. I'll see if I can bisect the fix. This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. Should be fixed in the next upstream release. We should re-enable the tests then. test_gdb is currently broken on Fedora 29 because of a gdb bug: bug #1639242 ( gdb fails to read debug symbols). It's a bug in gdb: see bz#1638798. gdb has been fixed in Fedora Rawhide: bz#1638798. The "py-bt" gdb command works as expected on python3 (python3-3.7.2-1.fc29.x86_64).
test_gdb pass on Python 3.6.8 and 3.7.2 (at least when compiled manually using "./configure && make").
Since this issue has been reported, I fixed multiple test_gdb bugs upstreams and fixes are part of 3.6.8 and 3.7.2 releases.
> It's a bug in gdb: see bz#1638798.
> gdb has been fixed in Fedora Rawhide: bz#1638798.
I'm sorry, I was confused. Fedora 29 and Rawhide don't use the same gdb version. gdb in Fedora 29 wasn't affected by the gdb bug of Rawhide.
we need to unskip it before we close this. > we need to unskip it before we close this. Alright. I planned to unskip the test after closing the issue, but I'm fine with keeping the BZ issue open until the package is updated. I wrote https://src.fedoraproject.org/rpms/python3/pull-request/89 but I have multiple issues to get this change merged... test_gdb still fails on arm and s390x: * armv7hl: https://bugzilla.redhat.com/show_bug.cgi?id=1196181 * s390x: https://bugzilla.redhat.com/show_bug.cgi?id=1678277 I plan to at least reenable test_gdb on x86-64 (in practice: reenable test_gdb on all archs except arm and s390x). I created https://src.fedoraproject.org/rpms/python3/pull-request/93 to reenable test_gdb. https://src.fedoraproject.org/rpms/python3/pull-request/93 has been merged into the f29 branch: https://src.fedoraproject.org/rpms/python3/c/4bcbcff606bcac5cc7cbccf1192a01f2f89b899c?branch=f29 Since the change only impacts the build of the package, the package release is not incremented. I close the issue. |