Skip to content

Fail when haddock fails by default #359

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

Merged
merged 1 commit into from
Dec 18, 2019

Conversation

balsoft
Copy link
Contributor

@balsoft balsoft commented Dec 10, 2019

We don't run haddock when there are no source files. Otherwise, if haddock fails, the build will fail as well.

We don't run haddock when there are no source files
Copy link
Collaborator

@angerman angerman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this work with cabal packages that conditionally (via a flag) end up having no modules?

@balsoft
Copy link
Contributor Author

balsoft commented Dec 11, 2019

@angerman can you give me an example of that?

I'd like to think it should work (I added a check), but I haven't tested.

@angerman
Copy link
Collaborator

It's one of the compat packages on hackage I believe. I'll try to find it.

@angerman
Copy link
Collaborator

I don't think it was this one: http://hackage.haskell.org/package/mtl-compat
but something similar. I guess compiling that with-f-two-point-one -f-two-point-two would produce an empty package? So while there would be haskell files in the package, nothing to run on for haddock?

@balsoft
Copy link
Contributor Author

balsoft commented Dec 12, 2019

@angerman Thanks, I will look at it. I guess the only way to fix this would be to parse the output of haddock and look at what errors were produced.

@balsoft
Copy link
Contributor Author

balsoft commented Dec 12, 2019

@angerman it builds with those flags on this branch.

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