progress monitoring and elapsed time in logs...

as discussed on irc it's important for a user to monitor progress of a build run. Based on experience with morph + ybd i recommend:

• some ongoing indicator of [current task/tasks required for this run/total tasks for target]
• ongoing indicator of total elapsed time since run started
• record elapsed time for each component task completion

Note that

• users may want to glance at current run status while it's running (so want to see current elapsed time)
• users may want to look at the timeline profile of a run later, which means having elapsed time in every line of the log is useful
• users may want to compare specific task times between machines/runs (which AWS machine gives me best time vs cost result?) and between components (which builds are taking most time, to optimise that build or maybe try to adjust dependencies etc)

IMO the current realtime clocks per task are shiny but not really useful, and the zeroes+blanks are taking up space that would be better used as snapshot of elapsed time when that logline was generated.