Reproducing CI test errors locally

Tooling Package Management
1

I am writing a new package, and seeing a CI error using Github Actions, that I don’t see locally in my development environment.

In a previous thread someone has suggested SSHing to the CI machine to debug this. However, I’d prefer to try to run the CI script locally, on my own machine (a MacOS laptop). Does anyone have advice on how to do this?

2

You can try using GitHub - nektos/act: Run your GitHub Actions locally 🚀, but good luck getting anything useful out of it, in my experience most of the time the problem is something specific to the environment on the runners, which act doesn’t reproduce faithfully.

1 Like