Description
While running github/codeql-action/analyze@v4 as part of the GitHub Actions workflow, the job log shows that the analysis is taking a long time (25 seconds or more). The slow step seems to be during or after CodeQL queries on GitHub Actions files, with notable delays in post-processing and SARIF file handling:
- While resolving threads, detected 4 CPUs in
/sys/fs/cgroup/cpuset.cpus.effective.
- Running queries for actions
- Post-processing SARIF files:
["/home/runner/work/react/results/actions.sarif"]
- Uploading code scanning results and creating bundle metadata
- Skipping upload of TRAP and dependency caches
- Waiting for processing to finish
Steps To Reproduce
- Run the CodeQL workflow (
github/codeql-action/analyze@v4) on the facebook/react repository.
- Observe that the step completes in 25+ seconds for the action analysis.
The current behavior
- The CodeQL analysis phase runs slowly (~25 seconds for GitHub Actions files scan and SARIF processing).
The expected behavior
- The CodeQL analysis should ideally run faster and not cause long wait times on CI runs.
To provide a more actionable report, could you clarify or add the following information:
- Does the problem consistently occur for every workflow run, or is it intermittent?
- Does this happen with specific versions of CodeQL or setup steps?
- Are there any related errors or warnings in the logs?
- What is the impact on your development or release process?
Any reproduction links (e.g., a GitHub Actions run log), relevant workflow YAML, or more details will help diagnose and resolve this performance issue.
Description
While running
github/codeql-action/analyze@v4as part of the GitHub Actions workflow, the job log shows that the analysis is taking a long time (25 seconds or more). The slow step seems to be during or after CodeQL queries on GitHub Actions files, with notable delays in post-processing and SARIF file handling:/sys/fs/cgroup/cpuset.cpus.effective.["/home/runner/work/react/results/actions.sarif"]Steps To Reproduce
github/codeql-action/analyze@v4) on the facebook/react repository.The current behavior
The expected behavior
To provide a more actionable report, could you clarify or add the following information:
Any reproduction links (e.g., a GitHub Actions run log), relevant workflow YAML, or more details will help diagnose and resolve this performance issue.