-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add .travis.yml and test target #12
base: master
Are you sure you want to change the base?
Conversation
Why not use haskell-ci (which is really good), using travis for ubuntu? Unless you can have multiple travis setups for nix and non-nix builds. We could potentially test-drive typhon here for nix |
@chessai I'll check out haskell-ci tonight, bigger issue is why cabal on ubuntu doesn't respect |
@chessai try passing the |
why is a travis build not triggering on the most recent commits? |
@chessai It is working again, but you added |
The log shows:
I think this is because of the |
okay, configure seems to succeed now. however, hspec-discover fails. |
Yes, I fixed that error on my machine by running |
most recent failure seems spurious (just adding hvr-ppa) |
changed |
use $WITHCOMPILER |
sorry, i keep forgetting that git with do weird things with '$'-prefixed strings. |
Now we're seeing real errors 🎉 |
okay, the library is building, but running anything is failing with:
|
That was fixed in #17 |
ok, rebasing |
once a build with 8.8.1 passes, i will re-add the older ghcs |
It seems that #23 forgot to also remove the tests for the Ord instance. |
looks like this isnt getting copied in properly |
It is strange. There are two builds, pr and push, and they give different outputs: |
hmm. that is strange. |
do i need to remove the Ord tests from the test suite? |
Yes, I think so. |
now we at least see the same error on both. |
Oh, I think I know how to fix this. The linux documentation of arrayfire mentions that you have to do this:
|
I think that is also the reason for the ld-options field in the cabal file. So another alternative we have is putting:
back in the cabal file. (not |
we could do that. would it be better instead to do |
Yes, that would also work. |
I don't know if it carries over from before-install to script, but we will see. |
me either. i should probably just do it right after the arrayfire script finishes. |
failure on push is spurious. |
actually, those have to be persisting, because a lot of them are actually used during install. so i'm less worried about that. for example, if the extension to PATH to include $CABALHOME/bin didn't persist, the hspec-discover failure would still be occurring. |
extending LD_LIBRARY_PATH worked. Test suite now fails with:
Which i think is a problem with floating point arithemtic |
🤔 |
perhaps we should add a |
push failure is spurious |
nice. it built and passed. |
added ghc 8.6.5 and 8.4.4. |
Configure fails on older ghcs/cabal 2.4. Havent looked into it. |
i am going to get arrayfire locally so i can test without travis. i don't know why configure is failing on older ghcs, but not 881 with cabal 3.0 |
I get a similar error message in #13 (comment). |
- use haskell-ci - download arrayfire installer and unpack to /opt/arrayfire/ - remove Ord tests from test suite - use shouldBeEps for comparing Array Double nix updates - change shellHooks to use runhaskell instead of cabal-v1 - extend LD_LIBRARY_PATH to include $AF_LIB - ghcid shellHook uses -fno-nocode - get tests to build and _almost_ pass
just trying to appease travis right now, because locally everything is fine. |
OK, we now have CI for GHC 8.4.4, 8.6.5, and 8.8.1. @noughtmare @dmjio please review when you have time. |
have to add back LAPACK/doctest tests |
No description provided.