Bug 1377983 - recipe page relative timestamps for results are wrong when recipe never started
Summary: recipe page relative timestamps for results are wrong when recipe never started
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 08:44 UTC by Dan Callaghan
Modified: 2020-06-02 11:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-02 11:40:09 UTC

Attachments (Terms of Use)
screenshot (96.07 KB, image/png)
2016-09-21 08:47 UTC, Dan Callaghan 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Dan Callaghan 2016-09-21 08:44:02 UTC 
If a recipe aborts without starting, the results are shown with a relative timestamp based on the current time, so always some negative number of hours.

There's no sensible relative time we can show (since it's supposed to be relative to the start of the recipe, but it never started). It should probably just be +00:00:00 instead. That is, the result timestamp should be relative to the time of the abort rather than the start time.
Comment 1 Dan Callaghan 2016-09-21 08:47:05 UTC 
Created attachment 1203184 [details]
screenshot

Example screenshot. Recipe aborted 27 minutes ago, the result appears as 
-00:26:34 which doesn't make much sense.
Comment 2 Martin Styk 2020-06-02 11:40:09 UTC 
Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>
Note You need to log in before you can comment on or make changes to this bug.