release builder-images `cedacc9933` #65

Merged

pipeline-bot merged 3 commits from _promote/cedacc993330 into main

2026-07-29 19:26:38 +00:00

pipeline-bot commented

2026-07-29 19:26:38 +00:00

Collaborator

No description provided.

pipeline-bot added 3 commits

2026-07-29 19:26:38 +00:00

fix(linux-kernel): gate reads arch/$SRCARCH, and fails when it cannot read at all e66f5a29ad

Caught by the first live BuildRun (linux-kernel-ci-h667z, 13s).

Two defects in the gate landed in d3aa310:

1. Wrong path. `make ARCH=x86_64` builds out of arch/x86, so the defconfig is
   arch/x86/configs/seanfarm_defconfig — not arch/x86_64/configs/. KARCH is the
   make ARCH, which is not the source-dir name on x86. Split out SRCARCH.

2. The gate was VACUOUS on that wrong path. Each check is
   `grep <sym> $SRC && ! grep <sym> .config`; when $SRC does not exist the
   first grep is non-zero, the && short-circuits, the if is false, and the loop
   reports "hard-gated symbols survived configure" having verified nothing.
   The build only failed later, incidentally, on the drift report's redirect.
   A gate that cannot read its input must fail, not pass — silently passing is
   worse than no gate because it reads as proof. Assert $SRC and .config are
   readable first.

pahole in kernel-builder:v9 is v1.31, comfortably over the 1.21 that
CONFIG_DEBUG_INFO_BTF needs for DWARF5, so BTF is genuinely supported.

Fixture-tested: green with BTF present; fails on a dropped BTF, on an
unreadable defconfig (regression test for defect 2), and on a missing pahole.

fix(node-bootc): retry dnf past EPEL stale-metadata 404s d2449e5881

This is what actually killed the v6.18.35-seanfarm26 release. The kernel built
fine; node-bootc — the `bootc switch` target, and so the thing a roll actually
boots — died at:

  Status code: 404 for .../epel/10z/.../bb9a3191...-primary.xml.zst
  Error: Failed to download metadata for repo 'epel'

EPEL rotates its repodata frequently and deletes the old hashed files at once.
repomd.xml is the index naming them, so a build reading a repomd even slightly
behind the current rotation requests a primary.xml.zst that no longer exists.

Probed rather than assumed: the pkg-cache is NOT at fault. Its cached repomd is
byte-identical to upstream, it holds index files only 1m with revalidate, the
file the build wanted 404s UPSTREAM too, and the one the current repomd names
returns 200 through the cache. The race is against EPEL itself; the cache only
widens the window. Confirmed transient — the identical install succeeded
unchanged minutes after the failure.

Retry up to 5 times with backoff. `dnf clean metadata` between attempts is what
makes it work: without it dnf re-reads the same stale repomd from /var/cache/dnf
and every retry fails the same way. A genuine outage still fails, loudly, after
5 tries.

node-bootc had not built successfully in 24 days. Leaving a kernel roll gated on
a coin flip against EPEL's sync schedule is not acceptable for the one path that
ships CVE-patched kernels.

Merge pull request 'merge fix/kernel-btf-assert (6da455d98a)' (#64 ) from fix/kernel-btf-assert into trunk cedacc9933

pipeline-bot merged commit cedacc9933 into main

2026-07-29 19:26:38 +00:00

pipeline-bot deleted branch _promote/cedacc993330

2026-07-29 19:26:38 +00:00

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

sean/builder-images!65

No description provided.

Rows
Columns

release builder-images cedacc9933 #65

release builder-images `cedacc9933` #65