Skip to content

Fix a bug where the CLI would abort due a fatal error when an invalid configuration file path was provided #19344

Fix a bug where the CLI would abort due a fatal error when an invalid configuration file path was provided

Fix a bug where the CLI would abort due a fatal error when an invalid configuration file path was provided #19344

Triggered via pull request July 29, 2024 13:01
Status Success
Total duration 19m 57s
Artifacts

test.yml

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

Annotations

2 warnings and 2 notices
test (Python 3.11, ubuntu-latest, 3.11)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: leafo/gh-actions-lua@v10, leafo/gh-actions-luarocks@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (Python 3.12, ubuntu-latest, 3.12)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: leafo/gh-actions-lua@v10, leafo/gh-actions-luarocks@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (Python 3.11, ubuntu-latest, 3.11)
gh-actions-lua: Cache restored: lua:5.4.4:linux:x64:
test (Python 3.12, ubuntu-latest, 3.12)
gh-actions-lua: Cache restored: lua:5.4.4:linux:x64: