Erik 994d52403f ci: stream tests on the Windows gate instead of the log-redirecting gate script ... The windows-gate job was marked failed while the work was still running: 20 dotnet processes were alive on the runner and a complete 8.7 MB App.Tests TRX was on disk after Forgejo had already recorded a failure. Cause: tools/run-release-gate.ps1 redirects every bounded child process to its own log file, so the workflow step emits no output for minutes. Forgejo treats a task that stops reporting as a zombie and fails it. The Linux job, which runs dotnet test directly, streamed continuously and produced real results. The Windows job now builds and then runs each test project directly with the same trait filter copied from the gate script's default, so output streams the whole time. run-release-gate.ps1 remains the canonical LOCAL gate, where its bounded-process/blame-hang machinery is the point. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-08-19 10:50:21 +02:00
..
ci.yml	ci: stream tests on the Windows gate instead of the log-redirecting gate script	2026-08-19 10:50:21 +02:00
smoke.yml	ci: extend smoke workflow with a real Linux build job	2026-08-19 10:20:27 +02:00