-
Notifications
You must be signed in to change notification settings - Fork 178
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 fails and requires containers dependency #607
Comments
Have you tried following the instructions in https://github.com/haskell/containers/blob/master/CONTRIBUTING.md? |
Well, that's not particularly hard as the only step suggested is to make sure that my stack version is >= 1.6.1 which it is. |
You have to stack build before you stack test in this case, I believe. Did
you try that?
…On Tue, Apr 16, 2019, 5:14 AM Felix Linker ***@***.***> wrote:
Well, that's not particularly hard as the only step suggested is to make
sure that my stack version is >= 1.6 which it is.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#607 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzi_VrPvXML0jO26p5vDDRl-6mpjl4-ks5vhZRogaJpZM4a5vDQ>
.
|
Yes, as I wrote in the OP
|
I observe the same behaviour (containers-master, But when I do as the error message suggests ( I guess the reason is that
The constraint mentioned in the last item was lifted (in |
There is still something strange going on here:
and
I can solve this by putting this in stack.yaml:
|
Oof, this still seems relevant:
#675 is related. Building, testing and benchmarking really shouldn't be so hard. We ought to properly document this too. |
Previously these commands would fail due to circular dependency issues. Fixes haskell#607, fixes haskell#671.
Previously this command would fail due to circular dependency issues. Fixes haskell#607, fixes haskell#671.
Hi there,
I tried running the stack build steps.
stack build
worked fine and resulted in the final output:However, running
stack test
andstack bench
failed. Both commands failed to find a matchingcontainers
dependency which is rather odd to me. I guess I should not take the steps recommended by stack:My stack version is:
...and you probably have already noted that I'm on Windows 10.
The text was updated successfully, but these errors were encountered: