[ryanduguid]

Summary

A stalled install test now fails within 10 minutes, and its log names the stage it reached.

 - name: Install, run and uninstall the MSI
+  timeout-minutes: 10

test-install.ps1 prints a line before each stage: installing, checking the CLI version, starting the app, stopping the app and uninstalling.

Evidence

• Before: 2 of 8 runs that reached this step after a build never finished. One lost its runner after 44 minutes; the other was still in progress after 15 minutes, when I cancelled it. Both jobs' logs return HTTP 404, and the script prints nothing until it passes.
• After: a healthy run has plenty of room: the 6 passing runs took 8 to 21 seconds. On 12 fresh runners with no build first, the test passed 12 of 12 in 11 to 23 seconds.

The cause of the stall is still unknown, and this change doesn't fix it. It won't help either if the runner itself dies.

Merge danger

Door: two-way. Blast radius: release CI

A healthy install test taking over 10 minutes would now fail the job and hold back the draft.

Unverified

The timeout has never fired, so a stall ending at 10 minutes is unconfirmed. Dry run 41149871873 of this commit passed all jobs: the step took 8 seconds after a full build and logged all 5 stages.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud