Closed tonyday567 closed 8 years ago
And, let me say while I'm waiting for the green light, once the cache kicks in in the new travis setup, the build takes all of 4 minutes.
Wow! Thank you sooooooo much! This is awesome!
I'd eventually like to get llvm back in there because it's pretty much required to get decent numerical speed from Haskell. But this is so much better than the current state of things. I'm very happy :)
I know very little about travis. Do you happen to know if there's a way to use a travis.yaml
file to automatically get a system configured the same way as the test suite? Either on AWS or on a VM. That would make deployments so much easier.
https://halcyon.sh/ might be what you're looking for. But I just fake sysdev - I copy pasted a yml from one of the stack guys projects.
It's probably best to turn llvm on as the default and turn it off in the travis run, but I couldn't quickly work that out.
38
I targeted the new container-based travis (sudo: false) and it neatened up the code well. Subject to llvm.
I had a good look through the whole llvm travis mess. llvm have turned off support for apt download; you can read about the detail here: https://github.com/travis-ci/travis-ci/issues/6120 So, to get the repo back to green, I turned off -fllvm in the cabal for bench. There's just one target: stack lts-6. I figured it would be better to keep the time down until some stability is reached.