Bug 9737

Summary: [PATCH] ui/knotty: give out start time of task
Product: [Build System, Metadata & Runtime] BitBake Reporter: Enrico Scholz <enrico.scholz>
Component: bitbakeAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: alex.kanavin, poky.bs.watcher, poky.watcher
Version: unspecified   
Target Milestone: 2.2 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
patch none

Description Enrico Scholz 2016-06-09 14:13:11 UTC
Created attachment 3222 [details]
patch

For long running tasks like compiling qt it might be interesting to know
when the task has been started.  Patch prints this information by using
the %X modifier (locale dependent presentation of time without date).
Comment 1 Richard Purdie 2016-09-22 12:53:44 UTC
I like this idea but I think there is a better thing to do which is to show task elapsed time. If we display the start time, the next thing the user will manually do is look at the current time and compare so we may as well do it for them. I'll send such a patch to bitbake-devel.
Comment 2 Enrico Scholz 2016-09-22 12:58:11 UTC
Showing the elapsed time means that display must be refreshed periodically.
Comment 3 Richard Purdie 2016-09-23 14:11:55 UTC
(In reply to comment #2)
> Showing the elapsed time means that display must be refreshed periodically.

Which we already do due to the progress changes anyway so this doesn't really add that much overhead. I did rate limit it to 5s rather than 1s intervals to try and reduce the refresh problem.

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=0d76de85bd2fa8fc6b0a3a5a65f2817a5d0b2186
Comment 4 Alexander Kanavin 2016-09-27 08:33:52 UTC
Sorry, have to reopen this. With the change, highlighting the terminal tab happens constantly, whereas previously it was highlighted only when a task has been finished. For people running long tasks in a edit-rib-debug cycle (i.e. me) that is an unpleasant regresssion, as now the terminal tab has to be polled to see if the task is done yet, whereas previously I could just glance at it while doing other stuff in a different tab.
Comment 5 Alexander Kanavin 2016-09-27 10:17:01 UTC
Okay, I found that the terminal provides a workaround for this. Let's open a separate issue for UI notifications using d-bus.