Skip to content

Produce separate SARIF file for quality-queries alerts #3332

Produce separate SARIF file for quality-queries alerts

Produce separate SARIF file for quality-queries alerts #3332

Triggered via pull request June 16, 2025 16:26
Status Failure
Total duration 1m 5s
Artifacts
Matrix: Go: workaround for indirect tracing
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Go: workaround for indirect tracing (ubuntu-latest, default)
Error running analysis for go: Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.22.0/x64/codeql/codeql database interpret-results --threads=4 --format=sarif-latest -v --output=../results/security/go.sarif --no-sarif-add-snippets --print-diagnostics-summary --print-metrics-summary --sarif-add-baseline-file-info --sarif-codescanning-config=/home/runner/work/_temp/user-config.yaml --sarif-group-rules-by-pack --sarif-include-query-help=always --sublanguage-file-coverage --sarif-run-property=jobRunUuid=6c9f0a66-7d67-4ca1-b9d8-2c915269a672 --sarif-run-property=incrementalMode=diff-informed --sarif-include-diagnostics /home/runner/work/_temp/codeql_databases/go". Exit code was 2 and error was: A fatal error occurred: Could not write SARIF file (eventual cause: NoSuchFileException "/home/runner/work/codeql-action/results/security/go.sarif"). See the logs for more details.
Go: workaround for indirect tracing (ubuntu-latest, default)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum