Skip to content

Slight improvement to computing clock resolution in benchmarking #813

Slight improvement to computing clock resolution in benchmarking

Slight improvement to computing clock resolution in benchmarking #813

Triggered via push July 22, 2024 08:14
Status Success
Total duration 9m 36s
Artifacts
Matrix: Linux Ubuntu 22.04 Bazel build <GCC 11.2.0>
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Linux Ubuntu 22.04 Bazel build <GCC 11.2.0> (dbg)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux Ubuntu 22.04 Bazel build <GCC 11.2.0> (fastbuild)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux Ubuntu 22.04 Bazel build <GCC 11.2.0> (opt)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/