Bug 1305754 - Incorrect dates are displayed on the build page.
Summary: Incorrect dates are displayed on the build page.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: clime
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-09 07:19 UTC by Bheesham Persaud
Modified: 2016-03-29 12:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-29 12:22:00 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bheesham Persaud 2016-02-09 07:19:09 UTC 
Description of problem:
The dates in the Submitted, Started, and Finished fields on the build status page are incorrect.

For this[1] build, the build submission date claims that it was submitted 2 days ago, but the date listed is "2014-01-13 19:25 UTC" -- definitely not 2 days ago.

[1]: https://copr.fedorainfracloud.org/coprs/fabiand/rust-unofficial/build/1043/


How reproducible:
Sometimes. Not all build pages seem to have this issue.


Steps to Reproduce:
1. Navigate to the "Builds" tab in a Copr project.
2. Click on a build ID to view detailed information about a build.
3. Verify if time makes sense.

Actual results:
2014-01-12 22:01 UTC (2 days ago) 

Expected results:
2014-01-12 22:01 UTC (2 years, 27 days ago)
OR
2016-02-07 22:01 UTC (2 days ago)
Comment 1 clime 2016-03-18 08:43:43 UTC 
Fixed by 13e7c7b6. Thank you!
Comment 2 Jakub Kadlčík 2016-03-21 11:59:59 UTC 
Code with this fix is currently deployed on testing server.
You can test it before it will be deployed to production.
Please see: http://copr-fe-dev.cloud.fedoraproject.org
Comment 3 Jakub Kadlčík 2016-03-29 12:22:00 UTC 
Copr production machines were upgraded to version containing a fix to this issue.
If you are not satisfied with provided solution, please feel free to reopen this.
Note You need to log in before you can comment on or make changes to this bug.