Windows jobs stalling at different points

Since a couple of days, the Windows jobs of my workflow are stalling. See this run, for example: https://github.com/brechtm/rinohtype/runs/1219576099

It sometimes gets stuck as early as the checkout step, so I don’t think it’s related to the workflow .yml contents.

@brechtm,

I noticed that all the Windows jobs were stuck at the “Install development dependencies” step when executing the command line “poetry install -vv --no-root”.

You can try to check with the following steps:

  1. Enable debug logging and run the workflow again to see if you can get more information from the debug logs.

  2. Check if you or other members in the repository have changed some configurations or settings in the workflow that may cause the problem.

  3. Try executing the steps with the same project on your local Windows machine to see if the command line “poetry install -vv --no-root” can work.

  4. If the command line “poetry install -vv --no-root” can work on your local Windows machine, install a self-hosted runner on the local Windows to run the workflow to see if the problem still occurs.

Any update, feel free to tell us.

Thank you, @brightran. It appears the exact position in the job where it’s stalled is only visible when the run has timed out. When it was still running, the Windows jobs appeared to be stalled at different points, but I assume this is just a side-effect of buffering?

@brechtm,

When it was still running, the Windows jobs appeared to be stalled at different points, but I assume this is just a side-effect of buffering?

Yes, during the job running, sometimes the UI can’t refresh in time with the latest status of each step.
In fact, all the Windows job were stuck at the “Install development dependencies” step, the previous steps seem to work well.

In addition, how about the check steps I mentioned above, did you find any helpful information from the debug logs?

I’m not exactly sure what the cause was, but it was related to the Poetry tool and cached files. The cache was invalidated due to changed files and the workflow seems to be running fine.