0s in queue, ran for 0s

[art-w]

Context

I don't understand the 0s timings displayed by the CI header on some jobs. The example link is coming from https://github.com/ocurrent/current-bench/pull/438/checks?check_run_id=13718052712 which has other jobs with understandable timings.

Steps to reproduce

• Go to https://ocaml.ci.dev/github/ocurrent/current-bench/commit/43c5f8cf5f7c5dfa7e1be4a50b904561c9af462c/variant/debian-12-4.14_arm64_opam-2.1
• Header displays "0s in queue", "Ran for 0s"
• Logs indicate different:

2023-07-31 15:44.43: New job: test ocurrent/current-bench https://github.com/ocurrent/current-bench.git#refs/heads/schema-infix-op (43c5f8cf5f7c5dfa7e1be4a50b904561c9af462c) (linux-arm64:debian-12-4.14_arm64_opam-2.1)
...
2023-07-31 15:44.43: Waiting for resource in pool OCluster
2023-07-31 17:06.50: Waiting for worker…
2023-07-31 17:22.45: Got resource from pool OCluster
...
2023-07-31 17:38.24: Job succeeded

Expected behaviour

16min in queue (or 1h32min?) Ran for 16min