Re: Running the Cabal tests

I would not worry too much about these; they're a bit touchy due to the use of symlinks. If you could figure out why they are failing that would be helpful though! Edward Excerpts from Erik de Castro Lopo's message of 2016-03-19 21:15:45 -0700: > Erik de Castro Lopo wrote: > > > These test

Re: Running the Cabal tests

Erik de Castro Lopo wrote: > These test don't fail when I'm building with ghc-7.10 (which was also used to > build GHC). Should these tests fail like that? Correction, these tests pass with ghc-7.10 on my laptop and fail on my Jenkins box. My laptop and Jenkins box are both x86_64/linux running

Re: Running the Cabal tests

Edward Z. Yang wrote: > Actually, the package test suite doesn't have to make this assumption > (it just does so by default). If you add CABAL_PACKAGETESTS_WITH_GHC > you can specify a version of GHC to do the tests with, distinct from > the GHC version Cabal was built with. (It works best if

Re: Running the Cabal tests

Edward Z. Yang wrote: > package-tests currently has a dumb hack to figure out these environment > variables: it tries to read out the local build information associated > with your build of Cabal. Thank you Ed. That explains some bizare behaviour I'm seeing. > Unfortunately, this format is

Re: Running the Cabal tests

Excerpts from Erik de Castro Lopo's message of 2016-03-19 19:24:34 -0700: > Edward Z. Yang wrote: > > > package-tests currently has a dumb hack to figure out these environment > > variables: it tries to read out the local build information associated > > with your build of Cabal. > > Thank you

Re: Running the Cabal tests

Excerpts from Mikhail Glushenkov's message of 2016-03-19 07:57:42 -0700: > Hi, > > On 19 March 2016 at 08:35, Erik de Castro Lopo wrote: > > Hi all, > > > > I hacked together what I thought was a neat little feature (a 3 line diff) > > and thought I'd add a test. Thats when

Re: Running the Cabal tests

Hi, On 19 March 2016 at 08:35, Erik de Castro Lopo wrote: > Hi all, > > I hacked together what I thought was a neat little feature (a 3 line diff) > and thought I'd add a test. Thats when I figured out I couldn't even run > the tests. > > Reading `Cabal/tests/Readme.md` I

Running the Cabal tests

Hi all, I hacked together what I thought was a neat little feature (a 3 line diff) and thought I'd add a test. Thats when I figured out I couldn't even run the tests. Reading `Cabal/tests/Readme.md` I see I need to set the environment var: > * `CABAL_PACKAGETESTS_GHC` is the path to the GHC you