Bug 1377983

Summary: recipe page relative timestamps for results are wrong when recipe never started
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: web UIAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: mastyk, mjia
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-02 11:40:09 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:
Attachments:
Description Flags
screenshot none

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>