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
I hate to pull all our eggs in on one basket called GitHub, but Travis has been rather slow, and it would be nice to share more stuff between Unix and Windows CI.
Maybe the first step is to have all 3 and see how they perform in practice?
I do not have enough repo permissions, however, to try this myself.
The text was updated successfully, but these errors were encountered:
Get CI on GitHub Actions via a patched workflow generated by haskell-ci.
- DEVELOPER.md explains how to regenerate the CI, e.g. in case of new GHCs.
- .github/haskell-ci.patch modifies the generated workflow by:
* Setting flag 'bootstrap' to False in calls to cabal.
* Installing happy instead of just building it.
* Setting HAPPY and HC for running the tests.
- tests/Makefile has been modified to not overwrite already set HAPPY
and HC variables. This is needed to locate these executables correctly.
- cabal.haskell-ci contains configuration for running haskell-ci:
It removes constraints on packages containers, mtl and transformers.
Otherwise, these will be constrained to the GHC-shipped versions,
which isn't compatible with happy for all GHC versions.
The logic behind this CI setup is identical to
haskell/alex#189
[fixeshaskell#189] [fixeshaskell#193]
I hate to pull all our eggs in on one basket called GitHub, but Travis has been rather slow, and it would be nice to share more stuff between Unix and Windows CI.
Maybe the first step is to have all 3 and see how they perform in practice?
I do not have enough repo permissions, however, to try this myself.
The text was updated successfully, but these errors were encountered: