Sarah Mount
Sarah Mount
Sounds good to me.
Many thanks @Ascension1231 that explains why my testing branch didn't find any actual errors :( At least now we know that is safer to merge when it's finished!
OK, I'll work out the statistics and come up with a more detailed proposal.
DECISION: Do this anyhow (!) but put the code in `extras/`
This sounds really neat. What do you propose for a machine readable format? CSV seems like the easiest format that handles columns and rows, but that excludes a multitime2csv extension...
DECISION: `multitime -n 100 -c 99 -t csv:/tmp/out.data ./myprog | extras/m2tex.py` `multitime -n 100 -c 99 -t csv:/tmp/out.data ./myprog | extras/m2html.py`
Perhaps I have misunderstood time. I thought 'real' was the wall clock time, 'user' was the time spent on the CPU in user mode, and 'sys' was the time spent...
I pushed a first go at this to a branch called "cputime".
OK, done.
+1 for the Laravel log driver, or perhaps you could mock sendmail in your unit tests?