Re: $REPORTTIME behaves weirdly on macOS

[Mikael Magnusson <mikachu@xxxxxxxxx>]

On 6/30/21, Marlon Richert <marlon.richert@xxxxxxxxx> wrote:
> % REPORTTIME=0
> % sleep 1
> sleep 1  0.00s user 0.00s system 0% cpu 1.008 total
> % REPORTTIME=1
> % sleep 1
> % REPORTTIME=0.99
> % sleep 1
> sleep 1  0.00s user 0.00s system 0% cpu 1.008 total
> % REPORTTIME=1.001
> % sleep 1
> % sleep 2
> % REPORTTIME=1.1
> % sleep 2
> % REPORTTIME=0.99
> % sleep 2
> sleep 2  0.00s user 0.00s system 0% cpu 2.006 total
> %
>
> What's going on here? It seems that when $REPORTTIME >= 1, no time
> output is ever produced.
>
> The exact values here are unique to sleep, but similar behavior can be
> observed for other commands, too, albeit at different thresholds.

REPORTTIME
 If  nonnegative,  commands  whose  combined  user and system execution
 times (measured in seconds) are greater than this  value  have  timing
 statistics  printed  for them.

Note the difference between elapsed time (total) and cpu time (user +
system) in your output.

-- 
Mikael Magnusson