Format elapsed time and critical path time

[marekkrk]

Description of the feature request:

Bazel currently formats elapsed build time and critical path time in seconds. Example:
Elapsed time: 23120.370s, Critical Path: 131.10s

It would be good to use human friendly formatting, for example:
Elapsed time: 6h 25m 20.370s, Critical Path: 2m 11.10s

Which category does this issue belong to?

CLI

What underlying problem are you trying to solve with this feature?

Usability

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 7.1.2

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[brentleyjones]

@katre most recently (iirc) tried to address this.

[nikhilkalige]

Similar request #17137

[katre]

I took a look at this a few months ago and didn't make much progress. The underlying issue was mostly down to code complexity: in various places we're using Duration, int, long, and double to hold data that is either Duration, seconds, or milliseconds, and trying to resolve it all was too complex.

I'd love to see better progress here, so don't let me discourage you, but there aren't any quick fixes to be had, unfortunately.

[oquenchil]

Duplicate of #17137