Skip to content

fix(ci): derive KVER from the defconfig instead of hardcoding it #48

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.

Sign up for GitHub

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

Merged
mcfbytes merged 1 commit into from
Jul 20, 2026
Merged

fix(ci): derive KVER from the defconfig instead of hardcoding it #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 24 additions & 1 deletion scripts/ci-tests.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,30 @@ LINUX_IMG="$IMAGES/linux.img"
# tree), and their presence in CI by build.yml's merged-kver assert. Do not
# "fix" these checks to glob across all trees; they would then pass on the
# variant tree while the main one regressed.
KVER=6.18.38
#
# DERIVED, never hardcoded. This was literally `KVER=6.18.38` until 2026-07-19,
# and it drifted the moment the kernel moved to 6.18.39: every module check
# below started looking in usr/lib/modules/6.18.38/, found nothing, and
# reported six failures that all read like the kernel-module packages had gone
# stale ("a kernel bump needs 'make <pkg>-dirclean'") when in fact the build was
# fine and only this constant was wrong. A hardcoded version here does not fail
# safe -- it fails *misleadingly*, pointing the reader at the wrong subsystem.
#
# Read the MAIN image's defconfig specifically, which is what the scoping note
# above is about: configs/mister_rt.fragment overrides this symbol for the RT
# variant, and configs/mister_kernel_defconfig carries a lockstep copy
# (scripts/check-kernel-defconfig-sync.sh asserts those two agree).
#
# Anchored to ^ and taking the last match on purpose: the defconfig explains
# this symbol in a comment that quotes it verbatim, so an unanchored match
# returns two lines -- the exact bug fixed in the hash-sync workflow (#42).
KVER=$(sed -n 's/^BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="\([^"]*\)".*$/\1/p' \
"$ROOT/configs/mister_de10nano_defconfig" | tail -1)
if [ -z "$KVER" ]; then
echo "FATAL: could not read BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE from" >&2
echo " $ROOT/configs/mister_de10nano_defconfig" >&2
exit 1
fi

# ---------------------------------------------------------------- reporting
PASS_COUNT=0
Expand Down
Loading