Skip to content

Implement dumping of processed sarif file #7117

Implement dumping of processed sarif file

Implement dumping of processed sarif file #7117

Triggered via pull request September 9, 2025 13:07
Status Failure
Total duration 9m 46s
Artifacts

__upload-ref-sha-input.yml

on: pull_request
Matrix: Upload-sarif: 'ref' and 'sha' from inputs
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 notice
Upload-sarif: 'ref' and 'sha' from inputs (ubuntu-latest, default)
Aborting upload: only one run of the codeql/analyze or codeql/upload-sarif actions is allowed per job per tool/category. The easiest fix is to specify a unique value for the `category` input. If .runs[].automationDetails.id is specified in the sarif file, that will take precedence over your configured `category`. Category: (.github/workflows/__upload-ref-sha-input.yml:upload-ref-sha-input/os:ubuntu-latest/version:default/) Tool: (CodeQL)
Upload-sarif: 'ref' and 'sha' from inputs (macos-latest, default)
Aborting upload: only one run of the codeql/analyze or codeql/upload-sarif actions is allowed per job per tool/category. The easiest fix is to specify a unique value for the `category` input. If .runs[].automationDetails.id is specified in the sarif file, that will take precedence over your configured `category`. Category: (.github/workflows/__upload-ref-sha-input.yml:upload-ref-sha-input/os:macos-latest/version:default/) Tool: (CodeQL)
Upload-sarif: 'ref' and 'sha' from inputs (windows-latest, default)
Aborting upload: only one run of the codeql/analyze or codeql/upload-sarif actions is allowed per job per tool/category. The easiest fix is to specify a unique value for the `category` input. If .runs[].automationDetails.id is specified in the sarif file, that will take precedence over your configured `category`. Category: (.github/workflows/__upload-ref-sha-input.yml:upload-ref-sha-input/os:windows-latest/version:default/) Tool: (CodeQL)
Upload-sarif: 'ref' and 'sha' from inputs (windows-latest, default)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677