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

stack test with detailed-0.9 fails (executable not found) #1429

Closed
michaxm opened this issue Nov 25, 2015 · 5 comments · Fixed by #1447
Closed

stack test with detailed-0.9 fails (executable not found) #1429

michaxm opened this issue Nov 25, 2015 · 5 comments · Fixed by #1447
Milestone

Comments

@michaxm
Copy link

michaxm commented Nov 25, 2015

Hi,

stack test does not execute the detailed-0.9 test suite, see minimal example (including working instructions for cabal-install):
https://github.com/michaxm/test-detailed-example

stack test
Test suite test-detailed-example-test executable not found for test-detailed-example
Test suite failure for package test-detailed-example-0.1.0.0
test-detailed-example-test: executable not found

Tested with 1.6 and current master, same result:

stack --version
Version 0.1.6.0, Git revision e22271f (2313 commits) x86_64
~/projects/stack/.stack-work/dist/x86_64-linux/Cabal-1.22.4.0/build/stack/stack --version
Version 0.1.9.0, Git revision 1482c5c (2663 commits) x86_64

@michaxm
Copy link
Author

michaxm commented Nov 25, 2015

related to #1399 ?

@mgsloan
Copy link
Contributor

mgsloan commented Nov 26, 2015

Yes, likely the same bug. I think it's worthy of another release (version 0.1.8.1).

Closing as a duplicate, please reopen if this also happens with the latest development version.

@luigy
Copy link
Contributor

luigy commented Nov 26, 2015

@mgsloan I don't think stack supports detailed-0.9 tests currently.
The process is a bit different and I'm surprised it took this long to come up unless I'm totally misinterpreting the code xD

In a detailed-0.9 test when searching for the test executable it should have "Stub" appended to name & dir and it should pass this in to have the test "run"

This will require knowing the TestSuiteInterface (from the cabal file unless we have this information ready somewhere else already) to run the test with the correct behavior

I can take this one if no one else is up

@mgsloan
Copy link
Contributor

mgsloan commented Nov 26, 2015

Ah, yes, you're right. Thanks for the repro @michaxm , somehow I missed the bit where you mentioned it also reproing on master.

@luigy Sure, a PR for this would be great!

@luigy
Copy link
Contributor

luigy commented Nov 28, 2015

pushed first working stab

ping @mgsloan for feedback

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

Successfully merging a pull request may close this issue.

3 participants