spack/lib/spack
Todd Gamblin be6bb413df spack solve: use consistent units for time
`spack solve` is supposed to show you times you can compare. setup, ground, solve, etc.
all in a list. You're also supposed to be able to compare easily across runs. With
`pretty_seconds()` (introduced in #33900), it's easy to miss the units, e.g., spot the
bottleneck here:

```console
> spack solve --timers tcl
    setup        22.125ms
    load         16.083ms
    ground        8.298ms
    solve       848.055us
    total        58.615ms
```

It's easier to see what matters if these are all in the same units, e.g.:

```
> spack solve --timers tcl
    setup         0.0147s
    load          0.0130s
    ground        0.0078s
    solve         0.0008s
    total         0.0463s
```

And the units won't fluctuate from run to run as you make changes.

-[x] make `spack solve` timings consistent like before
2022-12-26 22:28:44 +01:00
..
docs Add --fresh to docs to actually upgrade spack environments (#34433) 2022-12-22 11:19:24 +00:00
env Control Werror by converting to Wno-error (#30882) 2022-11-23 12:29:17 -08:00
external archspec: add support for zen4 (#34609) 2022-12-20 11:22:50 +01:00
llnl Windows: reenable unit tests (#33385) 2022-12-09 13:27:46 +00:00
spack spack solve: use consistent units for time 2022-12-26 22:28:44 +01:00
spack_installable Remove support for running with Python 2.7 (#33063) 2022-11-14 13:11:28 +01:00