-
Notifications
You must be signed in to change notification settings - Fork 691
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
Comments
@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! |
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.
This was referenced Oct 8, 2016
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.
Added in #3960. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@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:
cabal/cabal-install/Distribution/Solver/Modular/Log.hs
Line 86 in c116df4
cs
.I would add a unit test to Solver.hs. Here is an example of a test that checks for a specific error message:
cabal/cabal-install/tests/UnitTests/Distribution/Solver/Modular/Solver.hs
Line 45 in c116df4
The text was updated successfully, but these errors were encountered: