Write the warning census and the config differential of the Current set - #69
Merged
Merged
Conversation
This was referenced Oct 3, 2026
Merged
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.
gk publishnow writes two more pages from the store, both over the newest cell at every crossing of a Current kernel with an upstream GCC column.reports/warning-census.mdis the census of spec 11.5. Per configuration it has a table per GCC column (cells, warnings, warnings per cell, units, options, units under-Werror, fatal), a bar chart of warnings per cell, a table per warning option with the oldest and newest column that gives it, and the warnings on units built with-Werror. So far every published cell is clean: the only "warning" lines in the make logs are kbuild's own sha1sum echo, which never reacheswarnings.jsonl.reports/config-differential.mdis the differential of spec 11.3 on the Current set. For each platform and configuration, every kernel's.configis compared with the one of the next column that has a cell, and the symbols that change are gathered per step, with the kernels they changed on and both values.CC_VERSION_TEXTandGCC_VERSIONchange at every step and are left out.gk config-diffis still there for a single kernel.The README links both pages under the matrices, and spec 11.3 and 11.5 name the files.
Two things the first run of the differential shows:
2.47.20260726, and the kernel'sas-version.shreads the date as the patch level, so every cell with binutils 2.47 getsCONFIG_AS_VERSION=20285426. EveryAS_VERSION >=test passes either way, so nothing breaks yet. I'll open a finding for it.KUNIT_ALL_TESTS=y, so a step between an old and a new cell shows the KUnit options flipping. Those cells have a different config digest and the stripe queues rerun them, so this goes away by itself.