ci: drop the nightly-windev schedule; run the deep windev tier on demand
ci / portable (push) Failing after 10m10s
ci / java (push) Failing after 20m12s
ci / windows-x86 (push) Failing after 22m40s

The scheduled nightly-windev job failed most nights for host reasons and
filed a Gitea issue each time. Remove the cron trigger and the job, and add
a workflow_dispatch trigger whose windev_mode input (test/build/live) drives
the windows-x86 job, so the live tier runs on demand - from the Actions page
or via scripts/ci/run-windev-ci.sh live - the same way clients are packed and
published on demand. Docs updated to match.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Joseph Doherty
2026-11-15 09:42:13 -05:00
parent 26a90883fa
commit e74918ccfb
7 changed files with 65 additions and 85 deletions
+2 -2
View File
@@ -2,7 +2,7 @@
#
# TST-25: Linux side of the Windows/x86 Worker CI tier.
#
# Runs in the `windows-x86` / nightly Gitea jobs on a Linux runner (which always schedules,
# Runs in the `windows-x86` Gitea job on a Linux runner, or by hand for an on-demand run (which always schedules,
# unlike a broken Windows act_runner). SSHes to windev (10.100.0.48), where it fetches +
# checks out the SHA under test in the isolated CI clone C:\build\mxaccessgw-ci and runs
# scripts/ci/windev-worker-ci.ps1 there. The remote exit code propagates through
@@ -94,7 +94,7 @@ echo "run-windev-ci: mode=$MODE sha=$CI_SHA target=${WINDEV_SSH_USER}@${WINDEV_S
# It replaced a `New-Item -ItemType Directory` lock that was NOT mutually exclusive:
# PowerShell's directory provider checks for existence and then calls CreateDirectory (which
# succeeds on an existing directory), so two bootstraps starting together both "acquired" it.
# A scheduled run starts windows-x86 and nightly-windev in the same second, and on 2026-09-22
# A scheduled run used to start windows-x86 and nightly-windev in the same second, and on 2026-09-22
# (run 827) both got in, ran git concurrently and the nightly died on
# ".git/index.lock: File exists" (mxaccessgw#148/#150). A file handle is also released by the
# OS if the holder is killed (ssh drop, host reboot), so a dead run can never leave a stale