14d47919

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

Number the mutation progress lines by how many have started

The number in a progress line was the mutation's position in the manifest, and
the manifest's order is no longer the order the mutations are tested in: groups
run concurrently, and the most expensive of them are started first, so the
numbers arrived in the log out of order and in jumps of hundreds.  Telling a
reader how far along a run is is the only thing the counter is there for, and a
counter like that tells them nothing.

The number is now how many mutations have started, this one included, so it
climbs by one per line.  It is taken and written under the same lock, so the
lines reach the log in the order the numbers were handed out, and a debug run's
per-mutation diffs arrive whole rather than interleaved.  What this gives up is
that the number is no longer an identifier for the mutation it belongs to:
nothing needs it to be, because every line names the operator and the location,
and the report names each mutation it has anything to say about by id.
GitHub

Total

6s

Created Started Finished

Time to Start Worker time Duration Time to finish Idle
Config 18s 1s 1s 20s 18s
Eval 21s 3s 3s 25s 4s
Build - - - - -
Suite 18s 5s 6s 25s 23s

Timeline

Config Eval Failed Retried Compressed gap
0s20s