You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the Travis results of the latest builds (most recent one here), it looks like something goes wrong setting up the environment for the pre-commit command. See Travis output starting at:
Pushing changes doesn't trigger new Travis build. Perhaps @darrendignam or @carlwilson could have a look at this some time (I don't really understand Travis that well)?
Hi @bitsgalore how would you feel about moving the build to GitHub actions instead? We're now using that for most of our projects, it's a bit more modular and flexible, it's also quicker. If you're happy I'll get this done in the next weeks.
Looking at the Travis results of the latest builds (most recent one here), it looks like something goes wrong setting up the environment for the pre-commit command. See Travis output starting at:
https://app.travis-ci.com/github/openpreserve/jpylyzer/jobs/587417609#L424
And the root cause appears to be:
https://app.travis-ci.com/github/openpreserve/jpylyzer/jobs/587417609#L446
The pre-commit-hooks version is defined here. The 1.4.0 version specified there is pretty old (latest version is 4.3.0).
The text was updated successfully, but these errors were encountered: