This repository was archived by the owner on Aug 3, 2024. It is now read-only.
testsuite: Print haddock stdout/stderr on failure #1591
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This greatly helps when there are problems running haddock tests on GHC's CI because otherwise we get the very unhelpful error message: ``` Failed to run Haddock on test package '' ``` Now instead we also get the actual problem in the log: ``` haddock: internal error: /private/var/lib/gitlab-runner/builds/7KQsmDei/0/ghc/ghc/_build/install/lib/ghc-9.7.20230404/lib/../../../share/doc/ghc-9.7.20230404/html/libraries/array-0.5.5.0-inplace/array-0.5.5.0-inplace.conf.haddock: withBinaryFile: does not exist (No such file or directory) ```
|
Let me know if you feel it is still needed, and I'll migrate it to the GHC repo. :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This greatly helps when there are problems running haddock tests on GHC's CI because otherwise we get the very unhelpful error message:
Now instead we also get the actual problem in the log: