Repository navigation
ci(test-install): accept point-zero tarball names in latest-install verify - #61
Merged
Merged
Conversation
…erify
kernel.org drops the trailing .0 from point-zero stable tarballs: the
7.3.0 release ships as linux-7.3.tar.xz, so the verify grep for
linux-${ver}.tar.xz could never match and the first scheduled run
(39240990052) failed both latest-install jobs on a correct install.
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.
The first scheduled run of the workflow (39240990052,
main@0d1e3fa) failed both latest-install jobs atVerify installation— on installs that were actually fine. In both containers the installer resolvedStable: 7.3, downloaded and PGP-verified/opt/linux-kernel/linux-7.3.tar.xz, built, and installed kernel release7.3.0(/boot/vmlinuz-7.3.0present).Root cause is the verify step's own grep, not the installer:
grep -q "Downloaded and verified .*linux-${ver}\.tar\.xz" /var/log/kernel_installer.log${ver}is read back from/boot/vmlinuz-*→7.3.0, but kernel.org drops the trailing.0from point-zero stable tarballs:so the assertion could never match for an
x.y.0stable release. It passed on 2026-10-18 only because stable was7.2.11, where the tarball name equals the kernel release.Fix: strip a trailing
.0before matching (${ver%.0}). This keeps the original intent — the built release must be the one that was downloaded and PGP-verified:7.2.11is unchanged,7.3.0matcheslinux-7.3.tar.xz, and a real mismatch (e.g. built7.4.0vs downloaded7.3) still fails.Confirmation
workflow_dispatch@2895c31) — 11/12 green, including both latest-install jobs:Latest stable Debian 13 (trixie):+ grep -q Downloaded and verified .*linux-7.3\.tar\.xz /var/log/kernel_installer.log→Current stable kernel 7.3.0 installed successfully on Debian GNU/Linux 13 (trixie)Latest stable Fedora 44:Current stable kernel 7.3.0 installed successfully on Fedora Linux 44 (Container Image)Mainline Ubuntu 24.04 (noble), is an unrelated transient: it died unpacking thelinux-7.3-rc7.tar.gzgit.kernel.org snapshot (gzip: stdin: invalid compressed data--format violatedright after wget reported the file saved) — the same job passed on this same commit in the PR-triggered run 39258956640, andMainline Fedora 44was green in the same dispatch.pull_request).Local gates before push: 13/13
tests/test_*.shPASS, workflow YAML parses, IP guard clean.