build: split codeql runners into sections to try to reduce runtime headaches#8163
build: split codeql runners into sections to try to reduce runtime headaches#8163
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces three new CodeQL configuration files to partition the repository's analysis paths into autogenerated, handwritten, and repository-specific segments. The review feedback suggests further partitioning the 'packages' directory to effectively utilize parallel runners and avoid timeouts. Additionally, it is recommended to use 'paths-ignore' in the repository configuration to ensure full coverage of root-level files and other directories not explicitly covered by the other configurations.
| paths: | ||
| - 'packages' |
There was a problem hiding this comment.
If the packages directory is the primary contributor to the 6-hour runtime, moving it into its own configuration file will not resolve the timeout issue if it is still processed by a single CodeQL runner. To effectively reduce runtime and stay within the 6-hour limit, consider further partitioning the packages directory into multiple configuration files (e.g., by sub-directory ranges) to allow for parallel execution across multiple runners.
There was a problem hiding this comment.
I'll need to test with the split config before considering further splits.
1 participant
Continues the work started here: #8110
Currently trying to scan the entire repo in a cron job fails because it takes more than 6 hours.