-
Notifications
You must be signed in to change notification settings - Fork 1.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
JS/TS Analyse 2.20.4 Runs Extremely Slow #18736
Comments
Hi @aaronmassicotte, There's not a lot to go by here. Would you be able to share the codebase? If not the best option it to re-run the workflow with debugging enabled. This will generate some artifacts, including a database. When you download the artifacts you should be able to run the analysis locally. See here on how to do that. You want to pass |
output.log
summary.log
|
It doesn't look like any queries were run. What was the output of
? |
Initial Run
Subsequent run
|
Yeah, we cache results. You'll need to run |
I see you're not asking to verify whether a valid scan was run but looking to investigate the output of the uncached run. My mistake. I'm not sure what the intended outcome should be though, as this results in a very similar output: $
|
Those "No need to rerun" indicate that you didn't clear the cache. I'm still interested in the output from #18736 (comment), as the tuple counts in that log file should explain where the slowness is coming from. |
Oh, my mistake. You'll also need to pass |
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
The text was updated successfully, but these errors were encountered: