Repository navigation
workflows/build.yml: Fix related to prolonged use of the msys2 job - #20584
Conversation
To prevent the job from using the Windows Runner Image for an extended period (6 hours), the temporary solution is to:
- Use the previous setup-msys2 (GitHub Action to set up MSYS2).
https://github.com/msys2/setup-msys2
- Add the maximum number of minutes that the `msys2` job can run before GitHub automatically terminates it.
GitHub Actions timeout
https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes
Signed-off-by: simbit18 <simbit18@gmail.com>
|
|
Data from six recent msys2 runs, in case it helps: the hung ones (38116435520, 38116375368, 38117776252) and the good ones (38088288193, 38118616107, 38119950209) all used setup-msys2 ec48f7c5 and image windows-2025 20260901.588, so the pin may not be the cause. Every hung run stops in the first |
|
Hi @casaroli Based on the tests I've been able to run in the limited time I have, the problem doesn't occur when build Nuttx with Make, but only with CMake. It appears to be related to the updated version of the CMake package included in the latest version of MSYS2 New Old |
|
The process dump from #20590's run (38162235073) shows where it hangs: under |
Summary
I am currently investigating the issue with the MSYS2 job.
To prevent the job from using the Windows Runner Image for an extended period (6 hours), the temporary solution is to:
setup-msys2
msys2job can run before GitHub automatically terminates it.GitHub Actions timeout
Impact
Impact on user: NO
Impact on build: Use of the Windows Runner image (Job Msys2) for max 60 minutes.
Impact on hardware: NO
Impact on documentation: NO
Impact on security: NO
Impact on compatibility: NO
Testing
GitHub
https://github.com/simbit18/manual-nuttx-ci/actions/runs/38146000862/job/114489527281#logs