-
Notifications
You must be signed in to change notification settings - Fork 683
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
Attempt to avoid Haddock errors, make them nonfatal anyway #5459
Conversation
87118d2
to
6c505be
Compare
6c505be
to
6e407de
Compare
Nice, let's get this into 2.4. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK.
@@ -969,6 +969,15 @@ dieOnBuildFailures verbosity plan buildOutcomes | |||
maybeToList (InstallPlan.lookup plan pkgid) | |||
] | |||
|
|||
fail' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's call this helper dieIfNotHaddockFailure
or something similar.
d418022
to
7f59215
Compare
Haddock errors aren't fatal any more, but Cabal now knows not to invoke Haddock when there is no input for it to process.
7f59215
to
655daee
Compare
This seems to have broken #5977. Which is that you really do want haddock errors to be fatal when running |
Closes #5232.
Please include the following checklist in your PR: