testr adds timing data itself (using the same decorator). I've just
checked and it looks like it may be adding it at repository
serialisation time (post-muxing of parallel workers) which will lead
to entirely noddy times. So... we may need to move that to the front
of the pipeline within testr (but emitting timestamps at source is a
definitely good idea *anyhow*, so please do do that, these are
separate though related issues).
testr adds timing data itself (using the same decorator). I've just
checked and it looks like it may be adding it at repository
serialisation time (post-muxing of parallel workers) which will lead
to entirely noddy times. So... we may need to move that to the front
of the pipeline within testr (but emitting timestamps at source is a
definitely good idea *anyhow*, so please do do that, these are
separate though related issues).