Skip to content

Test get_started example #92

Test get_started example

Test get_started example #92

Triggered via schedule April 7, 2024 22:32
Status Failure
Total duration 3m 54s
Artifacts

build.yml

on: schedule
Matrix: build-and-run
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
build-and-run (GCC)
Resource not accessible by integration
build-and-run (CLANG)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-and-run (AC6)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-and-run (GCC)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-and-run (GCC)
Resource not accessible by integration
build-and-run (GCC)
Resource not accessible by integration
build-and-run (GCC)
Resource not accessible by integration
build-and-run (GCC)
Resource not accessible by integration
build-and-run (GCC)
Resource not accessible by integration
build-and-run (GCC)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
build-and-run (GCC)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.17.0.
build-and-run (GCC)
Resource not accessible by integration