mirror of
https://github.com/rsyslog/rsyslog.git
synced 2026-06-19 11:42:55 +02:00
87a0e984a9
Why: Fedora 42 and CentOS 8 still provide useful portability and image-drift signal, but they mostly duplicate adjacent PR runtime lanes. Keeping them in every PR makes the regular matrix slower without adding enough per-change confidence to justify the cost. The Debian sid PR lane no longer provides reliable rolling-Debian signal because its devcontainer image is not rebuilt frequently. Impact: Regular PR CI runs fewer duplicate or misleading distro lanes; daily CI keeps full configured coverage for the moved distro lanes and opens or updates tracking issues when scheduled lanes fail. Before/After: Before, centos_8, fedora_42, and a stale debian_sid image ran on every PR. After, centos_8 and fedora_42 run as full-suite daily distro lanes, and the stale debian_sid lane/container is removed. Technical Overview: Remove centos_8, fedora_42, and debian_sid from the run_checks.yml PR matrix. Add run_distro_daily.yml for full configured distro test runs using the same devcontainer images and configure options as the removed centos_8 and fedora_42 PR lanes. Delete the Debian sid devcontainer definition because an unreliably rebuilt sid image is a stale snapshot rather than a trustworthy upcoming-Debian canary. Do not apply PR relevance pruning to daily distro runs; scheduled runs must test the full configured lane because any code may have changed since the previous run. Use the same ci-failure artifact naming and log globs as regular PR CI so the flake collector can process scheduled failures through the same path. Add or align tracking issue reporting for the touched daily and weekly scheduled workflows so failures provide a persistent triage handle. Restrict tracking issue search to open issues so failures cannot update a closed tracker and become hidden. Clarify in issue summaries that failures must be classified as one-off flakes or regressions and that the long-term expectation is fewer flakes as recurring causes are fixed. Keep issue-write permission scoped to reporting jobs only. With the help of AI-Agents: Codex