The appliance gate has failed since 2026-09-26: tests/boot-test.sh does not exist #3

New issue

Open

opened 2026-09-28 02:23:15 -03:00 by marcos-mendez · 0 comments

marcos-mendez commented

2026-09-28 02:23:15 -03:00

(Migrated from github.com)

Opened 2026-09-28.

appliance / build-and-boot on this repository has never passed. It has
failed on every run since 2026-09-26 with the same error:

::error::tests/boot-test.sh is missing or not executable in this repository

Runs 36278621010 (2026-09-26, main) and 36376230342 (2026-09-28, a pull
request), same message both times. The nodejs-nginx layer itself is
published and answers 200 on the mirror, so the gate gets as far as pulling
and verifying it and then stops: this repository has no tests/boot-test.sh
for it to run.

Two days with nobody noticing is the point of this issue as much as the
missing file is. docs/traps.md of the handbook already records the shape:

A daily check reports drift every morning. Nobody reads it any more.

A red check nobody owns trains everyone to ignore red checks, and this
organization is about to have a second one on keel-redis, deliberately and
temporarily. Two standing reds is where the next real one goes unread.

What closes this: tests/boot-test.sh, executable, asserting what a booted
nodejs-nginx machine must be true about, in the shape the other appliance
repositories use. It is a stack layer, so the obvious floor is nginx
answering, node present at the declared version, and the service enabled and
surviving a restart.

If that is not going to be written soon, the honest alternative is to remove
the appliance job from .github/workflows/tests.yml until it is, so this
repository stops reporting a check it cannot satisfy. Either is fine. Leaving
it red and unowned is not.

Context: Keel-Linux/.github#12 renames this check to
appliance / boot-published-layer; the failure and this issue are unaffected
by the rename.

Opened 2026-09-28. `appliance / build-and-boot` on this repository has never passed. It has failed on every run since 2026-09-26 with the same error: ::error::tests/boot-test.sh is missing or not executable in this repository Runs 36278621010 (2026-09-26, `main`) and 36376230342 (2026-09-28, a pull request), same message both times. The `nodejs-nginx` layer itself is published and answers 200 on the mirror, so the gate gets as far as pulling and verifying it and then stops: this repository has no `tests/boot-test.sh` for it to run. Two days with nobody noticing is the point of this issue as much as the missing file is. `docs/traps.md` of the handbook already records the shape: > A daily check reports drift every morning. Nobody reads it any more. A red check nobody owns trains everyone to ignore red checks, and this organization is about to have a second one on keel-redis, deliberately and temporarily. Two standing reds is where the next real one goes unread. What closes this: `tests/boot-test.sh`, executable, asserting what a booted `nodejs-nginx` machine must be true about, in the shape the other appliance repositories use. It is a stack layer, so the obvious floor is nginx answering, node present at the declared version, and the service enabled and surviving a restart. If that is not going to be written soon, the honest alternative is to remove the `appliance` job from `.github/workflows/tests.yml` until it is, so this repository stops reporting a check it cannot satisfy. Either is fine. Leaving it red and unowned is not. Context: Keel-Linux/.github#12 renames this check to `appliance / boot-published-layer`; the failure and this issue are unaffected by the rename.