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

Print final conflict set when dependency solver fails after an exhaustive search #3570

Closed
grayjay opened this issue Jul 17, 2016 · 3 comments

Comments

@grayjay
Copy link
Collaborator

grayjay commented Jul 17, 2016

@kosmikus suggested showing this message at default verbosity because it is often more relevant than the summarized log.

EDIT:
The new message could go here:

(if exh then "Dependency tree exhaustively searched.\n"
This is where the solver prints a message after an exhaustive search. It already has access to the final conflict set, cs.

I would add a unit test to Solver.hs. Here is an example of a test that checks for a specific error message:

, runTest $ mkTest db22 "unknownPackage2" ["A"] (SolverFailure (isInfixOf "unknown package: C"))

@ezyang
Copy link
Contributor

ezyang commented Jul 17, 2016

@grayjay, if PR is welcome, could you edit your message to say where the code is that you would update to make this change, and how you would test it? Thanks!

@grayjay
Copy link
Collaborator Author

grayjay commented Jul 17, 2016

I realized that the hardest part of this issue is coming up with helpful wording. The task isn't as well-defined as I thought, so I removed the label.

fmthoma added a commit to fmthoma/cabal that referenced this issue Oct 8, 2016
Keep information about the final conflict set and print it in case of
exhaustive search. The original error message is not printed any more.
fmthoma added a commit to fmthoma/cabal that referenced this issue Oct 8, 2016
Conflicts are sorted by conflict counts, so high-rated conflicts appear
early in the list. Currently the raw count is printed.
fmthoma added a commit to fmthoma/cabal that referenced this issue Oct 9, 2016
Keep information about the final conflict set and print it in case of
exhaustive search. The original error message is not printed any more.
fmthoma added a commit to fmthoma/cabal that referenced this issue Oct 9, 2016
Conflicts are sorted by conflict counts, so high-rated conflicts appear
early in the list. Currently the raw count is printed.
fmthoma added a commit to fmthoma/cabal that referenced this issue Oct 10, 2016
Keep information about the final conflict set and print it in case of
exhaustive search. The original error message is not printed any more.
fmthoma added a commit to fmthoma/cabal that referenced this issue Oct 10, 2016
Conflicts are sorted by conflict counts, so high-rated conflicts appear
early in the list. Currently the raw count is printed.
fmthoma added a commit to fmthoma/cabal that referenced this issue Nov 11, 2016
Keep information about the final conflict set and print it in case of
exhaustive search. The original error message is not printed any more.
fmthoma added a commit to fmthoma/cabal that referenced this issue Nov 11, 2016
Conflicts are sorted by conflict counts, so high-rated conflicts appear
early in the list. Currently the raw count is printed.
fmthoma added a commit to fmthoma/cabal that referenced this issue Nov 21, 2016
Keep information about the final conflict set and print it in case of
exhaustive search. The original error message is not printed any more.
fmthoma added a commit to fmthoma/cabal that referenced this issue Nov 21, 2016
Conflicts are sorted by conflict counts, so high-rated conflicts appear
early in the list. Currently the raw count is printed.
fmthoma added a commit to fmthoma/cabal that referenced this issue Nov 29, 2016
Keep information about the final conflict set and print it in case of
exhaustive search. The original error message is not printed any more.
fmthoma added a commit to fmthoma/cabal that referenced this issue Nov 29, 2016
Conflicts are sorted by conflict counts, so high-rated conflicts appear
early in the list. Currently the raw count is printed.
@grayjay
Copy link
Collaborator Author

grayjay commented Dec 4, 2016

Added in #3960.

@grayjay grayjay closed this as completed Dec 4, 2016
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

3 participants