# Reproducing CI test errors locally

**URL:** <https://discourse.julialang.org/t/reproducing-ci-test-errors-locally/96045>\
**Category:** Package Management\
**Created:** [March 14, 2023, 10:28am UTC](https://discourse.julialang.org/t/reproducing-ci-test-errors-locally/96045 "2023-03-14T10:28:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![user664303](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/user664303/32/37843_2.png) [@user664303](https://discourse.julialang.org/u/user664303)\
**Post date:** [March 14, 2023, 10:28am UTC](https://discourse.julialang.org/t/reproducing-ci-test-errors-locally/96045/1 "2023-03-14T10:28:21Z")

</div>

I am writing a new package, and seeing a [CI error](https://github.com/ojwoodford/NLLSsolver.jl/actions/runs/4388248905/jobs/7684516533) 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](https://discourse.julialang.org/t/different-errors-on-ci-and-local-machine/83120/3) 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?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [March 14, 2023, 10:37am UTC](https://discourse.julialang.org/t/reproducing-ci-test-errors-locally/96045/2 "2023-03-14T10:37:28Z")

</div>

You can try using [GitHub - nektos/act: Run your GitHub Actions locally 🚀](https://github.com/nektos/act), 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.