Record the cost of allmodconfig and format the OOM check - #56
Merged
Merged
Conversation
tamnd
added
kind/docs
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
1 participant
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.
This answers open question 10 and finishes the OOM check that went into #55 by mistake.
The allmodconfig cell for 7.2.8 on x86_64 with gcc-16.2.0 compiled 26,633 units in 3 h 38 min on server2, against 12 to 43 min for defconfig+gk on the same machine. objtool on vmlinux.o was then OOM-killed while the machine was full (dmesg shows a global OOM with objtool at 3.5 GB RSS). Before this change gk recorded that as
failsand blamed the GCC. Now a make log with a recipe killed by SIGKILL (Error 137) leaves no cell behind, and search reports it as not run. That check reached main in the #55 publish commit because the publish script picked up my working tree. It had not been formatted, which is fixed here, and clippy and the tests pass. The publish script now refuses to run with a dirty tree.The settled answer: allmodconfig stays build-only and out of the stripe, and runs on demand for the newest Current kernel and the GCC 16 column, on x86_64 and arm64, on a host with memory to spare.