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

Error when running "stack install --test --coverage"? #1006

Closed
mgsloan opened this issue Sep 17, 2015 · 7 comments
Closed

Error when running "stack install --test --coverage"? #1006

mgsloan opened this issue Sep 17, 2015 · 7 comments
Milestone

Comments

@mgsloan
Copy link
Contributor

mgsloan commented Sep 17, 2015

Reported by Alfredo Di Napoli, in this PR.

Linking .stack-work/dist/x86_64-osx/Cabal-1.18.1.5/build/chronos-ctl/chronos-ctl ...
chronos-0.15.0.0: install
Installing executable(s) in
/Users/adinapoli/work/chronos/.stack-work/install/x86_64-osx/lts-2.16/7.8.4/bin
/Users/adinapoli/work/chronos/.stack-work/install/x86_64-osx/lts-2.16/7.8.4/hpc/: getDirectoryContents: does not exist (No such file or directory)

Can this be reproduced with a publicly accessible repo?

@adinapoli
Copy link
Contributor

To give you folks a bit more insights:

  • I did call stack install --coverage without the --test flag
  • This was a project I ported by not using stack setup but I manually created the stack.yaml
  • The project doesn't have a test suite or a test folder altogether.

Is it possible that the hpc folder is created as part of the initial stack bootstrapping and therefore that's the culprit?

@mgsloan
Copy link
Contributor Author

mgsloan commented Oct 7, 2015

Ah, this actually turned out to be a rather trivial thing to fix. Not sure why the problem wasn't obvious before, perhaps because it has nothing to do with the main coverage stuff. Pretty sure that the issue is that it's trying to create an index of all the hpc reports by listing the contents of a directory. The directory doesn't get created if no reports get generated.

Can you still reproduce the issue? Does the commit I've just pushed fix it? Please close if so :D Thanks!

@adinapoli
Copy link
Contributor

Hey @mgsloan , I will make sure to give this a spin as soon as I'll have a chance and report back (closing the issue in case). Thanks!

@adinapoli
Copy link
Contributor

@mgsloan Close enough! Now I'm getting a slightly different error:

screen shot 2015-10-07 at 11 29 11

@mgsloan
Copy link
Contributor Author

mgsloan commented Oct 7, 2015

@adinapoli Hah, doh! Fix pushed.

@adinapoli
Copy link
Contributor

Perfect, working as expected now! Thanks! Ps. I seems to not be able to close the issue! Please do!

@mgsloan mgsloan closed this as completed Oct 7, 2015
@mgsloan
Copy link
Contributor Author

mgsloan commented Oct 7, 2015

Awesome, thanks for trying my fixes!

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