Scheduled "Build and publish latest Zen Browser" workflow fails every run #79

New issue

Closed

opened 2026-10-01 10:23:20 +08:00 by Breadway · 1 comment

Breadway commented

2026-10-01 10:23:20 +08:00

Owner

How found: While waiting on unrelated breadbar CI (BAR-38), I listed recent Forgejo Actions runs across repos. bos's scheduled .forgejo/workflows/zen-browser.yml ("Build and publish latest Zen Browser") failed on every run I could see: runs 164 (2026-09-30 14:00), 168 (20:00), 172 (2026-10-01 02:00) and 173 (08:00), all failure.

Confidence: High that the workflow is failing (four consecutive scheduled runs reported failure by the API). Cause unknown: the job log endpoint returned "Not found" through the API, and I did not go onto hestia to read the runner logs.

Explanation: The six-hourly Zen poll is not producing a package, so the [breadway] repo's zen-browser-bin republish is not updated, and signed-repo.yml (which runs on this workflow's success) is not triggered by it. Impact: BOS users stay on whatever Zen version was last published. Next step: read the job log for run 173 in the Forgejo UI or on the runner and record the actual error here. Possibly related to the provenance work in BOS-78 ("The six-hour Zen poll still builds candidate updates"), not confirmed.

**How found:** While waiting on unrelated breadbar CI (BAR-38), I listed recent Forgejo Actions runs across repos. bos's scheduled `.forgejo/workflows/zen-browser.yml` ("Build and publish latest Zen Browser") failed on every run I could see: runs 164 (2026-09-30 14:00), 168 (20:00), 172 (2026-10-01 02:00) and 173 (08:00), all `failure`. **Confidence:** High that the workflow is failing (four consecutive scheduled runs reported `failure` by the API). Cause unknown: the job log endpoint returned "Not found" through the API, and I did not go onto hestia to read the runner logs. **Explanation:** The six-hourly Zen poll is not producing a package, so the `[breadway]` repo's zen-browser-bin republish is not updated, and `signed-repo.yml` (which runs on this workflow's success) is not triggered by it. Impact: BOS users stay on whatever Zen version was last published. Next step: read the job log for run 173 in the Forgejo UI or on the runner and record the actual error here. Possibly related to the provenance work in BOS-78 ("The six-hour Zen poll still builds candidate updates"), not confirmed.

Breadway added the

bug

labels

2026-10-01 10:23:20 +08:00

Breadway referenced this issue from a pull request that will close it,

2026-10-01 15:28:22 +08:00

Scheduled "Build and publish latest Zen Browser" workflow fails every run #80

Breadway commented

2026-10-01 15:28:32 +08:00

Author

Owner

Implemented the workflow dependency fix in PR #80. The retained runner logs for runs 1907 and 1949 show git: command not found (exit 127) during the first git config command. The workflow now installs git with its build dependencies. YAML parsing, the embedded shell syntax check, install-before-clone assertion, and git diff --check pass. I did not dispatch the workflow because it publishes to the live package registry.

Implemented the workflow dependency fix in PR https://git.breadway.dev/Breadway/bos/pulls/80. The retained runner logs for runs 1907 and 1949 show `git: command not found` (exit 127) during the first `git config` command. The workflow now installs `git` with its build dependencies. YAML parsing, the embedded shell syntax check, install-before-clone assertion, and `git diff --check` pass. I did not dispatch the workflow because it publishes to the live package registry.

Breadway closed this issue

2026-10-02 14:35:52 +08:00