Fix #4 (task scheduler scoring) closed but never built or deployed — no CI success, no JAR, mod absent from BMC5 #19

New issue

Closed

opened 2026-08-11 02:56:34 +00:00 by Mark · 1 comment

Mark commented

2026-08-11 02:56:34 +00:00

Owner

Finding

Issue #4 ("Task scoring system needs tuning") was closed on 2026-08-05 with fix commit 5257694f4a ("fix #4: tune task scheduler scoring") on main (branch head 78112592fc), but the fix was never built or deployed. There is no deployed artifact of mc-heroes-mod anywhere.

Source: kanban qa card t_e91b153c (probe findings, 2026-08-10).

Repro steps

Open the Forgejo Actions runs list for this repo: GET /repos/Mark/mc-heroes-mod/actions/runs?limit=25.
Confirm no run corresponds to fix head SHAs 5257694f4a / 78112592fc; run 5368 (plan-file commit) is cancelled.
Confirm all 32 workflow runs are failure or cancelled — no successful build has ever produced a JAR.
Check published artifacts: GET /repos/Mark/mc-heroes-mod/releases returns [] (no releases/tags); artifacts endpoint 404.
Check the BMC5 Minecraft server (the NeoForge 1.21.1 runtime this mod targets): the mods volume /data/mods (359 jars) contains no heroesmod jar (grep heroesmod = 0 matches). EpheroLib-1.21.1-NEO-FORGE-1.2.0.jar is a different mod, not this repo's build.

Actual vs expected

Expected: after fixit card t_a4d2d489 landed and #4 closed, the mod JAR is built by CI, published as an artifact/release, and installed on the BMC5 server where the fix is live.
Actual: the source-level fix is on main, but no JAR was ever built (CI never succeeded), never published, and never installed. BMC5 server is healthy (Up 2 months, RCON OK) but the mod is absent.

Impact

The fix is code-only; users of the mod have no way to obtain or run the fixed task-scheduler scoring. Closing #4 as fixed overstates what actually shipped.

Kanban card: t_e91b153c (this card)
Fixit card: t_a4d2d489
Issue #4: closed 2026-08-05
Issue #16: prior CI JDK failure (closed 2026-05-14) — CI has remained failing since.

## Finding Issue #4 ("Task scoring system needs tuning") was closed on 2026-08-05 with fix commit `5257694f4a` ("fix #4: tune task scheduler scoring") on `main` (branch head `78112592fc`), but the fix was **never built or deployed**. There is no deployed artifact of mc-heroes-mod anywhere. Source: kanban qa card `t_e91b153c` (probe findings, 2026-08-10). ## Repro steps 1. Open the Forgejo Actions runs list for this repo: `GET /repos/Mark/mc-heroes-mod/actions/runs?limit=25`. 2. Confirm no run corresponds to fix head SHAs `5257694f4a` / `78112592fc`; run 5368 (plan-file commit) is `cancelled`. 3. Confirm **all 32** workflow runs are `failure` or `cancelled` — no successful build has ever produced a JAR. 4. Check published artifacts: `GET /repos/Mark/mc-heroes-mod/releases` returns `[]` (no releases/tags); artifacts endpoint 404. 5. Check the BMC5 Minecraft server (the NeoForge 1.21.1 runtime this mod targets): the mods volume `/data/mods` (359 jars) contains **no** heroesmod jar (`grep heroesmod` = 0 matches). `EpheroLib-1.21.1-NEO-FORGE-1.2.0.jar` is a different mod, not this repo's build. ## Actual vs expected - **Expected:** after fixit card `t_a4d2d489` landed and #4 closed, the mod JAR is built by CI, published as an artifact/release, and installed on the BMC5 server where the fix is live. - **Actual:** the source-level fix is on `main`, but no JAR was ever built (CI never succeeded), never published, and never installed. BMC5 server is healthy (Up 2 months, RCON OK) but the mod is absent. ## Impact The fix is code-only; users of the mod have no way to obtain or run the fixed task-scheduler scoring. Closing #4 as fixed overstates what actually shipped. ## Related - Kanban card: `t_e91b153c` (this card) - Fixit card: `t_a4d2d489` - Issue #4: closed 2026-08-05 - Issue #16: prior CI JDK failure (closed 2026-05-14) — CI has remained failing since.

Mark added the

bug

label

2026-08-11 02:56:34 +00:00

Mark referenced this issue from a commit

2026-08-11 10:25:16 +00:00

fix #19, #20: CI workflow never succeeds — route to healthy runner, use Forgejo action mirror

Mark closed this issue

2026-08-11 10:25:17 +00:00

Mark commented

2026-08-11 11:28:45 +00:00

Author

Owner

CI is now green — first successful build in repo history (run #5519, commit bc96704, 5m39s, BUILD SUCCESSFUL, 16/16 tests, mod-jar artifact uploaded).

Root causes fixed:

No runner was registered for this repo. The three existing runners (localhost-runner, localhost-nodedesk-runner, localhost-kimi-runner) are repo-scoped to other repos, so every workflow run sat in waiting forever (web UI: "No matching online runner with label: linux"). Registered localhost-mcheroes-runner (id 27) via the repo registration-token endpoint — runs dispatch instantly now.
Workflow action refs used https://github.com/actions/*.git@v4 which never resolved on this instance (all 32 prior runs failed/cancelled). Switched to the Forgejo mirror https://data.forgejo.org/actions/*@<sha> (SHA-pinned, verified fetchable) — same pattern as nodedesk's green runs.
runs-on label: ubuntu-latest is claimed by a broken bare-binary runner on this instance (every job it claims dies with context canceled). Routed to linux — only the healthy containerized runners register it.

The #4 task scheduler scoring code itself was already sound — compiled and all 16 TaskSchedulerScoringTest cases passed in CI. Closing; the JAR is downloadable from run #5519 artifacts.

CI is now green — first successful build in repo history (run #5519, commit bc96704, 5m39s, BUILD SUCCESSFUL, 16/16 tests, `mod-jar` artifact uploaded). Root causes fixed: 1. **No runner was registered for this repo.** The three existing runners (localhost-runner, localhost-nodedesk-runner, localhost-kimi-runner) are repo-scoped to other repos, so every workflow run sat in `waiting` forever (web UI: "No matching online runner with label: linux"). Registered `localhost-mcheroes-runner` (id 27) via the repo registration-token endpoint — runs dispatch instantly now. 2. **Workflow action refs** used `https://github.com/actions/*.git@v4` which never resolved on this instance (all 32 prior runs failed/cancelled). Switched to the Forgejo mirror `https://data.forgejo.org/actions/*@<sha>` (SHA-pinned, verified fetchable) — same pattern as nodedesk's green runs. 3. **runs-on label**: `ubuntu-latest` is claimed by a broken bare-binary runner on this instance (every job it claims dies with context canceled). Routed to `linux` — only the healthy containerized runners register it. The #4 task scheduler scoring code itself was already sound — compiled and all 16 TaskSchedulerScoringTest cases passed in CI. Closing; the JAR is downloadable from run #5519 artifacts.