Created attachment 912592 [details] Traceback Fail Output Description of problem: ./python -m test -v returns FAIL for test_strptime due to time zone data incompatability Version-Release number of selected component (if applicable): 3.3.2-15 and 3.4.1 How reproducible: every time Steps to Reproduce: 1. use either rpmbuild -ba python3.spec or './python -m test -v' on independent built source tree 2. will get test fail 3. Actual results: fail for test_strptime Expected results: pass of test Additional info:
As asked for el7 bug in terminal DATE jsut returned Fri Jun 27 04:58:00 EDT
This is looking like ti might be a build system issue as koji.fedoraproject.org performs the same build using mock without an errors in the build log http://koji.fedoraproject.org/koji/taskinfo?taskID=7081742 Thanks Fenrus02. It is also strange to not that the tests which fail when running the whole suite './python -m test -v " will pass when run individually './python -m test -v testname'
I am trying to perform the mock build on local hardware which hosted the fc20 and el7 vm where the failed builds occurred.
Confirmation news and something of the direction this goes in. Folks at Centos-Devel using mock on a C7-rc system had similiar results and build fails to what I expereienced. Looks like possibly a C7rc issue. and or a C6 issue since C6 was hosting my F20vm which did not build.
rkuska can you attempt mock build of this src.rpm on an el7rc system and see if there are issues?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days