Message360892
> Is currently anybody actively working on this? Please, report what you have found out, if so. I'd like to start digging into this tomorrow and possibly avoid any duplicit work.
I tried but failed to reproduce the bug on Fedora 31 and Fedora Rawhide.
I tested 3.8 and master development branches on Fedora 31 x86-64 laptop: "./configure --with-pydebug CFLAGS=-O0 && make && ./python -m test -v test_zipfile" pass.
I tested Python 3.9.0a3 on my up-to-date Fedora Rawhide x86-64 VM: "./configure --with-pydebug CFLAGS=-O0 && make && ./python -m test -v test_zipfile" pass. I also tried to install Python in /opt/py39 and run tests using /opt/py39/bin/python3.9: the test still pass.
I also tested Python 3.9.0a3 on an up-to-date Fedora Rawhide ppc64 mock container: Python configured as the Fedora package does (LTO, PGO, CFLAGS, LDFLAGS, etc.). test_zipfile pass as well.
Since I cannot reproduce the issue, nor access a machine which the bug occurs, I don't know how to debug this issue.
Can I get access to "s390x Fedora Rawhide 3.x" buildbot worker?
I didn't try to rebuild Python using the Fedora specfile. I only built Python manually. |
|
Date |
User |
Action |
Args |
2020-01-28 18:38:43 | vstinner | set | recipients:
+ vstinner, David.Edelsohn, hroncok, Dormouse759 |
2020-01-28 18:38:43 | vstinner | set | messageid: <1580236723.48.0.175635186624.issue39460@roundup.psfhosted.org> |
2020-01-28 18:38:43 | vstinner | link | issue39460 messages |
2020-01-28 18:38:43 | vstinner | create | |
|