You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the issue is resolved. It is difficult to see why this is happening, but in our case the codebase is large (CodeQL scanned 8401 out of 8401 TypeScript files and 1568 out of 1569 JavaScript files in this invocation.). Normal runtime for this job is about 10 minutes with 32 GB memory and 40 (32 effective) CPUs
Let me know if I can help resolve the issue by providing additional details about the codebase. I suspect something in particular about this codebase may be running inefficiently, as no other JS/TS scans within the enterprise have been impacted so far
I've XPOSTED the issue in github/codeql#18736 as it may be the binary or the action's usage of it
The text was updated successfully, but these errors were encountered:
Pipelines had been taking >90m to run the CodeQL
github/codeql-action/analyze@v3
step sicne 2.20.4. When reverting back to 2.20.3 viathe issue is resolved. It is difficult to see why this is happening, but in our case the codebase is large (
CodeQL scanned 8401 out of 8401 TypeScript files and 1568 out of 1569 JavaScript files in this invocation.
). Normal runtime for this job is about 10 minutes with 32 GB memory and 40 (32 effective) CPUsLet me know if I can help resolve the issue by providing additional details about the codebase. I suspect something in particular about this codebase may be running inefficiently, as no other JS/TS scans within the enterprise have been impacted so far
I've XPOSTED the issue in github/codeql#18736 as it may be the binary or the action's usage of it
The text was updated successfully, but these errors were encountered: