-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The CodeQL analysis is broken due to the large content of the generated SARIF file #10203
Comments
Is it an option to temporary disable the codeql analysis until we have a solution? Currently the CodeQL analysis job in GH Action is keeping busy 1 runner for 40 minutes for each PR (out of 20 total runners available), this is seriously impacting every PR validation performance. |
@andreaTP please let's use this issue to discuss the solution. For requests like that, we can use other communication channels. |
I just found github/codeql-action#820, seems to be kind of the same issue. perhaps we should also post a failing workflow run there and see if they provide some sugggestions? Also, there seems to be some suggestions inside (just scanned over it, though) |
Update: The GitHub documentation states that For that, it's necessary to remove
You can find the complete file here. @JoshuaMulliken may have other ideas. If there's anything that you would like to suggest as a fix, please let us know. |
…ile (#10606) The issue was originally caused by high number of flows paths per alert generated by the LDAP federation module. That was identified taking the SARIF file generated and running: ``` jq '.runs[0].results | map({query_id: .rule.id, numPaths: .codeFlows | length})' java.sarif ``` Together we reduced the number of flows paths, adding optimizations to skip some paths and avoid false alerts. Co-authored-by: Bruno Oliveira da Silva <bruno@abstractj.com> Closes #10203 Co-authored-by: Joshua Mulliken <joshua@mulliken.net>
Describe the bug
The CodeQL analysis is broken due to the large content of the generated SARIF file.
Version
17.0.0
Anything else?
Ref: This is a follow up of #10108 (comment)
The text was updated successfully, but these errors were encountered: