Test suite uses c2hs found by the os.

[EJahren]

Currently the tests/system/cpp test is failing, looks like the lexer doesn't handle cpp directives correctly if directly after a comment.

Edit:
turns out I was using c2hs from .cabal (which I had modified) and not the one in dist.
Should the tests be changed to prevent this?

[ian-ross]

Interesting. What OS is this on? The test works fine on my Arch Linux system and on Travis.

[EJahren]

Oh, I was wrong about what caused the failure, turns out that the test system runs the version of c2hs installed on the system (which I had modified) and not the one residing in dist/. Maybe the best thing is to close this issue and maybe open a new issue for tests running unexpected (at least in my case) versions of c2hs.

[ian-ross]

You wouldn't believe the number of times I've been bitten by that sort of
thing...

On 3 May 2014 17:24, EJahren notifications@github.com wrote:

Oh, I was wrong about what caused the failure, turns out that the test
system runs the version of c2hs installed on the system (which I had
modified) and not the one residing in dist/.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/81#issuecomment-42107667
.

Ian Ross Tel: +43(0)6804451378 ian@skybluetrades.net
www.skybluetrades.net

[EJahren]

I would make an argument that the c2hs found by the system is not the right one to run in the tests since it might be os installed and not the one found in ~/.cabal. Also, in order to change it you need to run cabal install while in order to run the tests you would do cabal configure --enable-tests && cabal build && cabal test

[ian-ross]

I think you're right. The C2HS tests are a little funny that way. I'll
think about how to do it better -- I mostly avoid the issue by always
working in a hsenv sandbox and doing cabal install before running the
tests, but that's definitely not the best way.

On 3 May 2014 17:52, EJahren notifications@github.com wrote:

I would make an argument that the c2hs found by the system is not the
right one to run in the tests since it might be os installed and not the
one found in .cabal. Also, in order to change it you need to run cabal
install while in order to run the tests you would do cabal configure
--enable-tests && cabal build && cabal test

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/81#issuecomment-42108354
.

Ian Ross Tel: +43(0)6804451378 ian@skybluetrades.net
www.skybluetrades.net