The Security Hub probe on ghost-ci reads the newest successful runner-probe.yml run and
alerts after 26 h; the workflow had no schedule, so it never ran on its own.
The Security Hub server runs Debian forky; build-release.sh accepts forky and the
release matrix gains a debian:forky leg (~1 h more per release, legs run one at a
time). Testing moves: rebuild after a library transition.
The v0.2.6 trixie leg was cancelled by the job timeout at 60:04 (v0.2.5 took
~56 min on the single-CPU runner); the cold build + full suite outgrew it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each run takes about two hours on the one-core runner; queued main runs
delayed the v0.2.3 release build by hours.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Address code-review findings on this session's changes (no behavior change):
- Share the dense-slot index for the write->exec feature as
learn::kWriteExecFeatureIndex; featurize() and the model-score dev tool now
reference it instead of a duplicated literal 42 (prevents silent column drift
if the feature layout shifts).
- Fix the self_written_execs comments: the linkage is a GLOBAL bounded FIFO
(recent_writes), not strictly "this window" — the docs now match replay.cpp.
- release.yml: never cancel a tag/release run (cancel-in-progress only for
non-tag refs); push ordering doesn't guarantee the tag event arrives after the
branch event, so a same-sha branch push must not abort an in-progress release.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The single self-hosted runner ran the full matrix for BOTH a branch push and its
tag, so a commit's two runs fought for the one CPU (debian build failed on run 75
under that contention). Add:
- concurrency group keyed by sha + cancel-in-progress: a commit's tag run cancels
its branch run instead of competing;
- timeout-minutes: 60 on the build job so a wedged build fails cleanly;
- a best-effort ccache cache (CCACHE_DIR + actions/cache, continue-on-error) so
the cold single-CPU build goes warm/incremental when the runner has a cache
service (meson uses ccache automatically); harmless cold otherwise.
No daemon code changed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
release.yml builds, tests and packs a Linux install tree per distro
(debian:trixie, ubuntu:24.04), one at a time with JOBS=2 and nice.
Branches (main, ci/**) and PRs run the test lane and print each sha256;
a v* tag uploads the tarballs and .sha256 files to a draft release and
publishes it only when every build passed.
runner-probe.yml checks that a runner with the docker label picks up
jobs, can clone this repo with the job token and reach the API.
packaging/ci/build-release.sh is the shared build step. It refuses to
run outside CI because it installs packages.
Forgejo now reads .forgejo/workflows and ignores .github/workflows,
whose ubuntu-24.04/macos-15 labels no runner here provides.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>