Skip to content

Add logs around status report telemetry in init-post step #362

Add logs around status report telemetry in init-post step

Add logs around status report telemetry in init-post step #362

Triggered via pull request April 3, 2025 12:39
Status Success
Total duration 3m 10s
Artifacts 4
Matrix: Upload debug artifacts after failure in analyze
Download and check debug artifacts after failure in analyze
4s
Download and check debug artifacts after failure in analyze
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Upload debug artifacts after failure in analyze (nightly-latest)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (nightly-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.7.
Upload debug artifacts after failure in analyze (nightly-latest)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (nightly-latest)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (linked)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (linked)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.7.
Upload debug artifacts after failure in analyze (linked)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (linked)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (default)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (default)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.7.
Upload debug artifacts after failure in analyze (default)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (default)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.7.
Upload debug artifacts after failure in analyze (stable-v2.20.3)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum

Artifacts

Produced during runtime
Name Size Digest
my-debug-artifacts-default Expired
19.6 MB
sha256:112f11e621999c7846a9918fd2a8604918043cd6e5c89c54d876922a9740265f
my-debug-artifacts-linked Expired
19.7 MB
sha256:ded313049e64e41c451b6121c0fdd127f326f2085c1a0a73667bc8d8c8fd81c4
my-debug-artifacts-nightly-latest Expired
19.8 MB
sha256:b2fe452ddef1336d93927294d0c44847a6c7830a687b25f80e7b83e23d3bbdc0
my-debug-artifacts-stable-v2203 Expired
19.6 MB
sha256:8d31736cb4f58af6a93bcfde0d09107f39ae55887d67c80c7d34f7a6ab771f7f