Skip to content

Bump log visibility for failed analysis upload #1060

Bump log visibility for failed analysis upload

Bump log visibility for failed analysis upload #1060

Triggered via pull request August 15, 2025 16:57
Status Success
Total duration 7m 26s
Artifacts 4
Matrix: Upload debug artifacts after failure in analyze
Download and check debug artifacts after failure in analyze
17s
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 (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.22.3.
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
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.22.3.
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.22.3.
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.22.3.
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

Artifacts

Produced during runtime
Name Size Digest
my-debug-artifacts-default Expired
206 MB
sha256:8dccb5caf6558f003d425d9622dc6f835e6280ad572bcaf815cff3e49277f7f5
my-debug-artifacts-linked Expired
206 MB
sha256:dc3359512db22c042d19b82b6184aa4f4859fdb8834667df3407c519a82aaf28
my-debug-artifacts-nightly-latest Expired
206 MB
sha256:22b970e7bb4bcbd268f63e87dd87f3a5d1e46b42cf514360f2727eb4f1883d14
my-debug-artifacts-stable-v2203 Expired
20 MB
sha256:67d4e38aff2efdeb5b454ce56021219203e86b5b02e4639ffa6773f58e650bc0