Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1103776
| Summary: | Invalid date error in parse_date (from file datefmt.py) on some i18n tests. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Éric Fintzel <efintzel> |
| Component: | trac | Assignee: | Gwyn Ciesla <gwync> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | fschwarz, gwync, lmacken |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-26 09:13:02 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: | 1051573 | ||
*** This bug has been marked as a duplicate of bug 1107459 *** |
Description of problem: Invalid date error in parse_date (from file datefmt.py) on some i18n tests. Version-Release number of selected component (if applicable): trac-1.0.1-4.fc21.src.rpm How reproducible: Mock build with make check active. Actual results: File "/builddir/build/BUILD/Trac-1.0.1/trac/util/datefmt.py", line 466, in parse_date date=text, hint=hint), _('Invalid Date')) The error occurs in several i18n tests. Additional info: Looking at the https://kojipkgs.fedoraproject.org//work/tasks/717/6910717/build.log log file and reproducing the problem, I found the following defects describing the same problem: http://trac.edgewall.org/ticket/11290 http://trac.edgewall.org/ticket/11258 It seems using a version of trac more recent than 1.0.1 should help.