Skip to content
Build

Use different parallel test runner to avoid ugly stack traces #258

Sign in to view logs

Use different parallel test runner to avoid ugly stack traces

Use different parallel test runner to avoid ugly stack traces #258

Triggered via pull request July 8, 2024 08:56
@mrolouxmroloux
synchronize #112
matti/use-different-paralllel-test-runner
Status Success
Total duration 2m 54s
Artifacts –

build.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test (3.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.3)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, zcong1993/setup-timezone@master. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, zcong1993/setup-timezone@master. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/