ci: bump CCACHE_MAXSIZE to 600M

[UdjinM6]

Issue being fixed or feature implemented

A simple commit like bac6bfa should result in at least 90%+ cache hit.

But it's not the case for some jobs:
~22%: https://github.com/dashpay/dash/actions/runs/20113011572/job/57715279431
~25%: https://github.com/dashpay/dash/actions/runs/20113011572/job/57715279411

What was done?

Bump CCACHE_MAXSIZE to 600M

How Has This Been Tested?

Running CI on develop twice after this change:
~94%: https://github.com/UdjinM6/dash/actions/runs/20118156411/job/57736628182
~94%: https://github.com/UdjinM6/dash/actions/runs/20118156411/job/57736628179

Breaking Changes

n/a

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

[github-actions]

✅ No Merge Conflicts Detected

This PR currently has no conflicts with other open PRs.

[coderabbitai]

Walkthrough

A single environment variable configuration in the GitHub Actions build workflow is modified. The CCACHE_MAXSIZE parameter in .github/workflows/build-src.yml is increased from 400M to 600M, allowing the C compiler cache to retain more data during the build process.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file modified with one parameter value change
• No logic, control flow, or functional behavior alterations
• Straightforward configuration adjustment with no side effects to verify

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ci: bump CCACHE_MAXSIZE to 600M' directly and clearly summarizes the main change: increasing the CCACHE_MAXSIZE environment variable from 400M to 600M in the CI configuration.
Description check	✅ Passed	The description is directly related to the changeset, providing context about low cache-hit rates, the solution of bumping CCACHE_MAXSIZE to 600M, and evidence of improved performance from testing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bac6bfa and ae8464e.

📒 Files selected for processing (1)

• .github/workflows/build-src.yml (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

{guix-build*,releases,**/guix-build*,releases/**,.github/**,depends/**,ci/**,contrib/**,doc/**}

📄 CodeRabbit inference engine (CLAUDE.md)

Do not make changes to build system files (guix-build*), release artifacts, or avoid changes to .github, depends, ci, contrib, and doc directories unless specifically prompted

Files:

• .github/workflows/build-src.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Lint / Run linters
• GitHub Check: Build container / Build container

🔇 Additional comments (1)

.github/workflows/build-src.yml (1)

93-93: Config change aligns with PR objectives and testing.

The increase from 400M to 600M addresses the reported low cache-hit rates and matches the testing improvement (~94% hit) documented in the PR description.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[PastaPastaPasta]

This doesn't make a ton of sense to me; why is 400M not enough? I think when I did a build, I found the cache from a single build less than or around 50M

[UdjinM6]

This doesn't make a ton of sense to me; why is 400M not enough? I think when I did a build, I found the cache from a single build less than or around 50M

You are probably confusing it with depends cache which is around 50MB https://github.com/dashpay/dash/actions/caches?query=key%3Adepends, ccache one is much larger https://github.com/dashpay/dash/actions/caches?query=key%3Accache.

[PastaPastaPasta]

The ccache one is much larger; but I took a new docker container, installed ccache, built and saw usage around 50MB I think

[UdjinM6]

Wiped ccache cache on my remote node and rebuilt develop after make clean.

Cache size (GB): 0.6 / 10.0 ( 6.46%)

$ du -hd0 .cache/ccache/
618M	.cache/ccache/

[UdjinM6]

sqlite CI jobs started to fail sometimes with No space left on the device at Run unit tests step after this patch, #7075 should fix it by freeing 3GB+.

[kwvg]

utACK ae8464e

[PastaPastaPasta]

utACK ae8464e