test: refresh current kernel sweeps - #131
Merged
Merged
Conversation
ErenAri
force-pushed
the
agent/refresh-enterprise-kernels-august
branch
from
August 9, 2026 14:44
19721db to
14995aa
Compare
Contributor
Author
|
Merge-timing decision: the maintainer explicitly asked to finish remaining work without waiting for Campaign 2. This change is limited to validated profile/catalog evidence and generated documentation; it does not modify application code or |
35 tasks
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.
Summary
Refreshes the generated kernel-sweep catalog and committed validation baselines against the live kernel-crawler inventory as of 2026-08-09.
5.14.0-687.36.1.el9_8profiles5.14.0-731.el9.189and.187, lockdown.189, and minimal5.15.0-1105-kvm6.8.0-139Merge timing
Draft: do not merge before scheduled v0.4 Campaign 2 completes. This PR does not change the active
latest-kernel-sweepgraduation matrix or application code, but holding it avoids introducing any catalog/evidence churn immediately before the scheduled campaign.No tracking issue is required.
KVM evidence
All 10 current kernel targets passed the real static libbpf validator with zero required failures and zero infrastructure errors.
294e66d92324f65118345ebdf56b5c0c85668fbe5d3ad6d441c29ff9ecfcc7ce2d90b59117df6340f715269dd7f8346fb77cd6a9e801336f8e303c92eca9932806e324ef0b51452f02d787afb26ab3b8c14151808ea3cdfb36f7495e0af14fb4c75532c4b12e48007aa714c1819daf9020f19015382b881435cbc2f9282db69c7c8d66cbf12e4b5a877e0c458aee8a939d6de390a4931e3ef40098e931d3707eRemaining vendor-image lag
The live oracle still reports two honest stale snapshots:
5.10.260-259.1054, repository newest is.10616.1.176-223.369, repository newest is6.1.177-224.371Both current public images passed validation. Amazon package sweeps are not supported by the current generator, and no newer public KVM image containing those repository kernels was available. This PR deliberately does not claim validation for bytes that were not booted.
Validation
unameverification, and libbpf load/attach validation across 10 current targetsgo test ./...BPFCOMPAT_DOCS_COMPARE=worktree make check-docs-driftmake profile-catalog-auditgit diff --check