Skip to content
Jest Unit Tests

[NoQA] fix: timing measurements are inaccurate #86317

Sign in to view logs

[NoQA] fix: timing measurements are inaccurate

[NoQA] fix: timing measurements are inaccurate #86317

Triggered via pull request September 6, 2024 11:28
@hannojghannojg
synchronize #48654
margelo:chore/fix-timing-measurement
Status Success
Total duration 3m 5s
Artifacts –

test.yml

on: pull_request
Storybook tests
2m 56s
Storybook tests
Matrix: jest
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
test (job 1)
The following actions use a deprecated Node.js version and will be forced to run on node20: SimenB/github-actions-cpu-cores@31e91de0f8654375a21e8e83078be625380e2b18. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (job 3)
The following actions use a deprecated Node.js version and will be forced to run on node20: SimenB/github-actions-cpu-cores@31e91de0f8654375a21e8e83078be625380e2b18. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (job 2)
The following actions use a deprecated Node.js version and will be forced to run on node20: SimenB/github-actions-cpu-cores@31e91de0f8654375a21e8e83078be625380e2b18. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/