Repository navigation
ci: bound the coordinated upgrade e2e step and keep its log - #523
andrebrait wants to merge 1 commit into
Conversation
Twice on windows-latest the step ran until the 60-minute job limit and GitHub kept no log. Give it 25 minutes, write the suite output to a file (a detached process holding the step pipe keeps a Windows step open) and upload it when the step fails.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
The "Native compiled coordinated upgrade and rollback" step stalled on windows-latest until the 60-minute job limit twice (main run 44136326452 attempt 1, #520 run 44197018381), and GitHub kept no log, so the cause is unknown.
timeout-minutes: 25on the step (each test is already bounded at 15 min).$RUNNER_TEMP/compiled-upgrade.logwith stdin from /dev/null, then is printed: a detached process (update worker, host) that inherits the step pipe keeps a Windows step open after bun exits.compiled-upgrade-<os>.No product code changes.
Summary by CodeRabbit