casaroli opened a new pull request, #20590: URL: https://github.com/apache/nuttx/pull/20590
## Summary The msys2 builds take about 15 minutes, but some runs hang in the first configuration until GitHub cancels the job after 6 hours. The log stops at `Select WINDOWS_MSYS=y` and does not show what does not end (see the data in #20584). This PR adds a watchdog to the msys2 build step. If the builds still run after 20 minutes, the job prints every process with its command line, in a collapsed log group, and again every 10 minutes: - `ps -efW` (MSYS2 processes and Windows processes) - `Get-CimInstance Win32_Process` from PowerShell (process ID, parent ID and full command line) A normal run does not change. The watchdog stops within 30 seconds after the builds end, and the step keeps the exit code of `cibuild.sh`. It works together with the 60 minute timeout of #20584. ## Impact CI only. The msys2 job prints more output when it runs longer than 20 minutes. ## Testing A test workflow on `windows-latest` with the same `setup-msys2` setup ran the same block with a 1 minute threshold and a 3 minute dummy build that fails with exit code 3: https://github.com/casaroli/nuttx/actions/runs/38161759958 - The process lists came at 1 and 2 minutes. They show the whole tree, from `Runner.Worker.exe` through `msys2.CMD` and `bash` to `sleep 180`, with command lines. - The step ended 4 s after the dummy build, with exit code 3. `tools/checkpatch.sh -c -u -m -g` passes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
