Skip to content

Draft: load scenarios at runtime #505

Draft: load scenarios at runtime

Draft: load scenarios at runtime #505

Triggered via pull request October 20, 2024 19:18
Status Failure
Total duration 53s
Artifacts

lts.yml

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

Annotations

2 errors and 4 warnings
build (19, ubuntu-20.04)
Process completed with exit code 1.
build (21, ubuntu-20.04)
Process completed with exit code 1.
build (19, ubuntu-20.04)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (19, ubuntu-20.04)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (21, ubuntu-20.04)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (21, ubuntu-20.04)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/