Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Travis to haskell-ci #39

Closed
RyanGlScott opened this issue Mar 19, 2018 · 4 comments
Closed

Upgrade Travis to haskell-ci #39

RyanGlScott opened this issue Mar 19, 2018 · 4 comments

Comments

@RyanGlScott
Copy link
Member

Currently, the Travis script is using a hacky setup that should probably be replaced with haskell-ci. I've made an effort to do so on the tests-in-separate-component branch. Because the dependencies of the test suite depend on deepseq, we have to put the tests in a separate .cabal file to work around haskell/cabal#5200, à la haskell/primitive#90 and ekmett/transformers-compat#33.

Alas, that branch currently is failing to build. It's always the same failure, when trying to build time:

cabal: can't find include file HsTimeConfig.h

I don't know how to fix this, so I'm giving up for now.

@RyanGlScott
Copy link
Member Author

It looks like this is a cabal new-build–specific issue. See haskell/cabal#5223.

Until that can be resolved, it seems we're blocked here.

@RyanGlScott
Copy link
Member Author

As noted on haskell/cabal#5169, a workaround for this issue is downgrading to cabal-install-2.0. That makes some of the build configurations work, but there's still issues on GHC 7.4 and 7.6. Here's an example build failure to puzzle over.

@RyanGlScott
Copy link
Member Author

Rats, I think the GHC 7.4 and 7.6 build errors observed in #39 (comment) are caused by cabal-install-2.0 having a worse solver than 2.2, since with cabal-install-2.2, I'm able to successfully construct a build plan on 7.4 and 7.6. Unfortunately, I can't actually build it due to haskell/cabal#5223, so we're once again stuck on that.

@chessai
Copy link
Member

chessai commented Sep 1, 2021

We should just use GitHub actions now, which should work fine, especially when we drop 7.x support. Please re-open if I'm wrong.

@chessai chessai closed this as completed Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants