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

Add --max-backjumps to .travis.yml #917

Merged
merged 1 commit into from
Mar 8, 2018

Conversation

phadej
Copy link
Contributor

@phadej phadej commented Mar 7, 2018

No description provided.

@phadej
Copy link
Contributor Author

phadej commented Mar 7, 2018

Configuring library for warp-3.2.13..
Preprocessing library for warp-3.2.13..
Building library for warp-3.2.13..
Network/Wai/Handler/Warp/Response.hs:45:8:
    Could not find module ‘Data.Streaming.Blaze’
    Perhaps you meant
      Data.Streaming.Zlib (from streaming-commons-0.2.0.0)
      Data.Streaming.Text (from streaming-commons-0.2.0.0)
    Use -v to see a list of the files searched for.
cabal: Failed to build warp-3.2.13 (which is required by test:spec from

@jkarni
Copy link
Member

jkarni commented Mar 7, 2018

Yeah, I started seeing this yesterday too, after a cabal update. Looks like a new version of streaming-commons was released without the module, and I guess later versions of warp don't use it?

I'm 👍 on this, though I've been wondering, what's the usual way of making cabal's life easier (without increasing max-backjumps)? Is it to just have fewer dependencies and narrower version ranges?

@phadej
Copy link
Contributor Author

phadej commented Mar 7, 2018

In fact in this case also --reorder-goals helps solver to find a valid install plan.

@jkarni
Copy link
Member

jkarni commented Mar 7, 2018

Opened an issue here.

@phadej phadej merged commit c767efe into haskell-servant:master Mar 8, 2018
@phadej phadej deleted the travis-max-backjumps branch March 8, 2018 12:43
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

Successfully merging this pull request may close these issues.

2 participants