Portability CI: use the runner image's Node and Python, timeout 60 #119

Merged
libby merged 3 commits from libby/ci-setup-time into main 2026-11-11 21:55:31 +00:00 AGit
Member

Skips setup-node and setup-python on the Linux forge runner (the image carries Node 24.19.0 and Python 3.12.3; the actions re-downloaded both, about 4.5 minutes, run 639 vs 1378 timestamps), checks the versions, installs the Python packages into a venv (the image's Python is PEP 668 managed; run 1372 failed there), and sets timeout-minutes: 60. The Windows dispatch leg keeps both setup actions.

Measured: the node+python block 04:30:56 to 04:35:25 in run 639 is gone in run 1378. The dotnet SDK download (6.4 min vs 0.6) and checkout (4.4 vs 1.6) vary with the network and are unchanged by this PR. Run 1378 was cancelled at 30:02 by the runner's own cap, which Eureka raises to 60 after window B; the job value in the file must match, and the comment says so. Steps after the cap (pack test, TS verifier, mesh-ts, browser, C# vectors, HTTPS interop) did not run in CI; they use node and sys.executable-resolved Python, which Soul checked.

Merged on Soul (no blocking defect in the interpreter change; its F1 is the external runner cap) plus the earlier green steps of run 1378 (Python 219 OK, Rust, TS cache, Mesh churn), because the portability job cancels at timeout. Local C# and TS runs were not rerun: the diff touches only the workflow.

🤖 Generated with Claude Code

Skips setup-node and setup-python on the Linux forge runner (the image carries Node 24.19.0 and Python 3.12.3; the actions re-downloaded both, about 4.5 minutes, run 639 vs 1378 timestamps), checks the versions, installs the Python packages into a venv (the image's Python is PEP 668 managed; run 1372 failed there), and sets `timeout-minutes: 60`. The Windows dispatch leg keeps both setup actions. Measured: the node+python block 04:30:56 to 04:35:25 in run 639 is gone in run 1378. The dotnet SDK download (6.4 min vs 0.6) and checkout (4.4 vs 1.6) vary with the network and are unchanged by this PR. Run 1378 was cancelled at 30:02 by the runner's own cap, which Eureka raises to 60 after window B; the job value in the file must match, and the comment says so. Steps after the cap (pack test, TS verifier, mesh-ts, browser, C# vectors, HTTPS interop) did not run in CI; they use `node` and `sys.executable`-resolved Python, which Soul checked. Merged on Soul (no blocking defect in the interpreter change; its F1 is the external runner cap) plus the earlier green steps of run 1378 (Python 219 OK, Rust, TS cache, Mesh churn), because the portability job cancels at timeout. Local C# and TS runs were not rerun: the diff touches only the workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Portability CI: use the runner image's Node and Python, job timeout 60
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Failing after 4m57s
bfeca2fd52
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Portability CI: install the Python packages into a venv (the image's Python is externally managed)
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
44f54b8015
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Portability CI: the timeout comment names the runner cap that still binds
All checks were successful
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 23m17s
3b1c39fd76
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
libby merged commit 871d81807b into main 2026-11-11 21:55:31 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
GameCult/CultLib!119
No description provided.