Skip to content

CODEQL_ACTION_CLEANUP_TRAP_CACHES is not working #2885

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

Open
hsbt opened this issue May 2, 2025 · 5 comments
Open

CODEQL_ACTION_CLEANUP_TRAP_CACHES is not working #2885

hsbt opened this issue May 2, 2025 · 5 comments

Comments

@hsbt
Copy link

hsbt commented May 2, 2025

From #2030 (comment)

CODEQL_ACTION_CLEANUP_TRAP_CACHES is not working now. CodeQL generate 300M+ cache each CI build. We always have trouble with the amount of limit by this problem.

Does anyone show how to run with debug mode with CodeQL with above action?

@hvitved
Copy link

hvitved commented May 2, 2025

Hi. Here are some instructions on how to run CodeQL in debug mode.

@hsbt
Copy link
Author

hsbt commented May 7, 2025

@hsbt
Copy link
Author

hsbt commented May 14, 2025

Ruby core team are in real trouble with this issue. But there is no solution today for this.

I added automated purge step for TRAP cache at ruby/ruby#13330.

@adityasharad
Copy link
Contributor

Could you please try setting trap-caching: false in the with: section of the github/codeql-action/init step? That should disable the feature entirely.

@hsbt
Copy link
Author

hsbt commented May 23, 2025

@adityasharad Thanks for your advice. I added trap-caching: false to our workflows. I will share that results after a few weeks later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy