Portability CI: use the runner image's Node and Python, timeout 60 #119
Loading…
Reference in a new issue
No description provided.
Delete branch "libby/ci-setup-time"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
nodeandsys.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