#16277: Make JUnit report stdout/stderr in more cases -------------------------------------+------------------------------------- Reporter: mpickering | Owner: (none) Type: task | Status: new Priority: normal | Milestone: Component: Compiler | Version: 8.6.3 Keywords: newcomer | Operating System: Unknown/Multiple Architecture: | Type of failure: None/Unknown Unknown/Multiple | Test Case: | Blocked By: Blocking: | Related Tickets: Differential Rev(s): | Wiki Page: -------------------------------------+------------------------------------- In https://gitlab.haskell.org/ghc/ghc/merge_requests/210 we made a start to improve the junit output to also include stderr/stdout when appropriate. However, the patch only handles a few cases, it is reasonably straightforward to handle more cases but the refactoring was a bit more involved than I was prepared to do at the time. To find more places, look in `testlib.py` and grep for `failBecause`. There are examples such as `bad stderr` and `bad stdout` which would also benefit from reporting the stderr. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/16277 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler