e0b1cecf

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Say when, say what, and show the loop turning

Every line carries how long the command had been running when the line was
written, at a fixed width, so what happened when is readable afterwards.

The steps named phases rather than what was happening in them. They now
say which files the two halves are, that the first is uploaded and reset
into and the second imported, which export is being read and what it is
being compared against, and where the record is written. Every command run
on the router is printed as it runs, which is the detail those steps were
hiding.

Both waits print every attempt rather than once, because a wait that
prints once looks the same as one that has hung, and with the timestamps
the repetition is what says how long it has been going.

meta.mainProgram on the package, so lib.getExe stops warning twice per
evaluation about guessing it.

Total

6m13s

Created Started Finished

Time to Start Worker time Duration Time to finish Idle
Config 0s 1s 1s 1s 0s
Eval 1s 32s 32s 33s 0s
Build 32s 5m40s 5m41s 6m13s 0s
Suite 0s 6m14s 6m13s 6m13s 0s

Timeline

Config Eval Build
0s1m2m3m4m5m6m