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

Different results of stack build on travis-ci and appveyor #4334

Closed
hanjoosten opened this issue Oct 3, 2018 · 6 comments
Closed

Different results of stack build on travis-ci and appveyor #4334

hanjoosten opened this issue Oct 3, 2018 · 6 comments

Comments

@hanjoosten
Copy link

My project has a transitive dependency on hspec-discover. It builds fine with stack on travis-ci. However, the build with appveyor fails.

On appveyor, it fails with a "ignoring (possibly broken) abi-depends field for packages" warning. This might be somehow related with haskell/cabal#5465 . Both build with ghc 8.4. Stack uses linux, appveyor uses windows.

How can it be that one build goes well, and the other one fails?? And even more important, how can I get appveyor to succeed building the project?

Stack version

Method of installation

appveyor and travis-ci

@mihaimaruseac
Copy link
Contributor

Seems to be a windows issue

@hanjoosten
Copy link
Author

On my own laptop (Windows 10), if I build the project with stack install, the build is succesful. There same "ignoring (possibly broken) abi-depends field for packages" warning is produced, but that doesn't stop the build.

@hanjoosten
Copy link
Author

This is since we've upgraded to ghc 8.4. With ghc 8.2.2 there was no problem. This is becoming pretty nasty. Is there anything I could do to investigate what is going on?

@mihaimaruseac
Copy link
Contributor

Sorry for the delay in answering. I guess you could try changing the compiler but keeping the same stack version and snapshot and see if that causes the bug to go away.

Basically, we need to isolate if the error comes from GHC, stack snapshot or stack binary

@hanjoosten
Copy link
Author

For as far as I can see, this is related with the bug discussed in https://ghc.haskell.org/trac/ghc/ticket/14381. It says that it should be solved with ghc 8.6.1. Unfortunatly, I have too many dependencys that currentyly don't complile with 8.6 yet.

@mihaimaruseac
Copy link
Contributor

So it's a GHC bug, not a Stack one. Closing the issue, thanks for confirming.

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

No branches or pull requests

2 participants