test-linux fails on `MISSING: hero_proc` tooling-check (pre-existing) #18

New issue

Open

opened 2026-05-06 18:17:50 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-06 18:17:50 +00:00

Owner

Overview

tests.yaml step Verify installations fails on every push to development (and on every PR) with:

=== Tool Availability Report ===
Tools:
  OK: btrfs
  OK: nerdctl
  OK: cloud-hypervisor
  OK: buildctl
  MISSING: hero_proc
  OK: redis-cli
  OK: psql
  OK: buildah
  OK: iperf3
ERROR: 1 critical tools missing!

The runner image (ghcr.io/despiegk/builder:latest) doesn't ship hero_proc. The test environment expects it to be installed beforehand — either as a service-container side-car or via an explicit install step.

How this surfaced

Filed during session 65 of the home#212 build-binaries arc. Discovered on https://forge.ourworld.tf/lhumina_code/hero_lib_rhai/actions/runs/75 (test-linux on PR #17). Visible in every preceding test-linux run on this repo too. Not introduced by session 65 work — pre-existing.

Sister of hero_lib#134 which tracks the same kind of CI rot in hero_lib.

Why we're filing it now

Session 65 was unblocking the first release tag (PR #17). lint-linux is now green, build-linux will run when v0.1.0-rc3 is tagged. test-linux is the only remaining red — and it's not blocking because it doesn't gate tag-triggered builds. Filing this so it's tracked, not silently ignored.

Acceptance

Decide whether tests.yaml should run with hero_proc installed (likely yes — the engine integration tests need it) or skipped
If yes: add hero_proc install to the runner setup step in tests.yaml, OR run it as a service container, OR fetch the binary from the v0.4.4 release on lhumina_code/hero_proc
Green test-linux on development and on PRs

lhumina_code/hero_lib#134 — same kind of debt in hero_lib
Failing run: https://forge.ourworld.tf/lhumina_code/hero_lib_rhai/actions/runs/75

## Overview `tests.yaml` step **Verify installations** fails on every push to `development` (and on every PR) with: ``` === Tool Availability Report === Tools: OK: btrfs OK: nerdctl OK: cloud-hypervisor OK: buildctl MISSING: hero_proc OK: redis-cli OK: psql OK: buildah OK: iperf3 ERROR: 1 critical tools missing! ``` The runner image (`ghcr.io/despiegk/builder:latest`) doesn't ship `hero_proc`. The test environment expects it to be installed beforehand — either as a service-container side-car or via an explicit install step. ## How this surfaced Filed during session 65 of the home#212 build-binaries arc. Discovered on https://forge.ourworld.tf/lhumina_code/hero_lib_rhai/actions/runs/75 (test-linux on PR https://forge.ourworld.tf/lhumina_code/hero_lib_rhai/pulls/17). Visible in every preceding test-linux run on this repo too. **Not introduced by session 65 work — pre-existing.** Sister of [hero_lib#134](https://forge.ourworld.tf/lhumina_code/hero_lib/issues/134) which tracks the same kind of CI rot in hero_lib. ## Why we're filing it now Session 65 was unblocking the first release tag (PR #17). lint-linux is now green, build-linux will run when v0.1.0-rc3 is tagged. test-linux is the only remaining red — and it's not blocking because it doesn't gate tag-triggered builds. Filing this so it's tracked, not silently ignored. ## Acceptance - [ ] Decide whether `tests.yaml` should run with `hero_proc` installed (likely yes — the engine integration tests need it) or skipped - [ ] If yes: add `hero_proc` install to the runner setup step in `tests.yaml`, OR run it as a service container, OR fetch the binary from the v0.4.4 release on `lhumina_code/hero_proc` - [ ] Green test-linux on `development` and on PRs ## Related - https://forge.ourworld.tf/lhumina_code/hero_lib/issues/134 — same kind of debt in hero_lib - Failing run: https://forge.ourworld.tf/lhumina_code/hero_lib_rhai/actions/runs/75