Repository navigation
feat: build-tree.sh compiles through ccache when CCACHE_DIR is set - #25
Merged
Merged
Conversation
…s overpressure/linux's check builds do; kernel.md describes the layers' checks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
overpressure/linux's check builds compile the whole kernel every time (about 22 minutes), even for a change to one driver.
build-tree.sh: withCCACHE_DIRset, the compiler runs through ccache (CC="ccache aarch64-linux-gnu-gcc",CCACHE_COMPILERCHECK=content, 3 GB). The objects carry over to the next build, also from another checkout, and the end of the build prints the hit rate.CCACHE_DIRnothing changes. A release's two builds pass none, since they are the test that the kernel is reproducible.ccache gcc -vis gcc's own.docs/kernel.md:build-tree.sh's row says how the repository's CI uses it.phoenix/7.2, the Layers workflow starts its own pull requests' builds, and the rulesets requireci.It takes effect with overpressure/builder#4 (ccache in the image, released and pinned in overpressure's
overpressure/linux.py) and overpressure/linux's CI passingCCACHE_DIRfor check builds (the follow-up PR intocommon/7.2).Checks
bash -npython scripts/check-private.py --repo devices/phoenix --history)Hardware
Not needed. A full kernel build with ccache was not run locally; the first two check builds on GitHub after all parts are in show the hit rate.