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

Saturnin-0.1.0.1 fails its test suite #3

Closed
peti opened this issue May 18, 2015 · 2 comments
Closed

Saturnin-0.1.0.1 fails its test suite #3

peti opened this issue May 18, 2015 · 2 comments

Comments

@peti
Copy link

peti commented May 18, 2015

Citing from http://hydra.cryp.to/build/862105/log/raw:

Test suite documentation: RUNNING...
documentation: cabal: readCreateProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
Test suite documentation: FAIL

Apparently, the test suite assumes that cabal-install is installed, but that's not the case in our build environment. If the package relies on a certain build tool being available, then that dependency must be declared in a Build-Tools: attribute of the test suite stanza.

@jan-matejka
Copy link
Owner

[pid 17200] execve("/home/yac/data/hd/saturnin.git/.cabal-sandbox/bin/cabal", ["cabal", "haddock"], [/* 55 vars */]) = -1 ENOENT (No suc
h file or directory)
[pid 17200] execve("/home/yac/.gems/bin/cabal", ["cabal", "haddock"], [/* 55 vars */]) = -1 ENOENT (No such file or directory)
[pid 17200] execve("/home/yac/.local/go/bin/cabal", ["cabal", "haddock"], [/* 55 vars */]) = -1 ENOENT (No such file or directory)
[pid 17200] execve("/home/yac/.cabal/bin/cabal", ["cabal", "haddock"], [/* 55 vars */]) = -1 ENOENT (No such file or directory)
[pid 17200] execve("/home/yac/.local/bin/cabal", ["cabal", "haddock"], [/* 55 vars */]) = -1 ENOENT (No such file or directory)
[pid 17200] execve("/usr/local/bin/cabal", ["cabal", "haddock"], [/* 55 vars */]) = -1 ENOENT (No such file or directory)
[pid 17200] execve("/usr/bin/cabal", ["cabal", "haddock"], [/* 55 vars */] <unfinished ...>

I see. Comes from our tests/Haddock.hs.

But how come you get an error and I don't in my setup?

@jan-matejka
Copy link
Owner

It fails to build for me when I put there either "cabal" or "cabal-install". It appears build-tools is matched against an internal registry so cabal knows how to handle it.

See the first reply at haskell/cabal#1466

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants