Ben I'm still getting framework failures from the testsuite, as below. But now it's not just me: it's CI! See !2600 which is failing in this way. It'd be good to nail this... it seems wrong to have to ignore framework failures when checking that a build validates. Simon | -----Original Message----- | From: Simon Peyton Jones | Sent: 20 April 2020 21:42 | To: Ben Gamari <ben@well-typed.com> | Subject: RE: T13456 | | Thanks! | | | -----Original Message----- | | From: Ben Gamari <ben@well-typed.com> | | Sent: 20 April 2020 18:57 | | To: Simon Peyton Jones <simonpj@microsoft.com>; ghc-devs <ghc- | | devs@haskell.org> | | Subject: Re: T13456 | | | | Simon Peyton Jones via ghc-devs <ghc-devs@haskell.org> writes: | | | | > I'm getting this failure (below) from validate fairly consistently. | | > It is often silenced by adding an empty file | | > ghci/should_run/T13456.stderr But it's troubling. Does anyone else | see | | this? How can I debug it? | | > | | Indeed this is odd. I have not seen this in CI or my local builds. It's | | possible that I have seen it in local builds that were failing for | other | | reasons but ignored it. | | | | While I don't know why you are seeing these failures in general, the | fact | | that they are reported as framework failures is arguably a bug. I would | | argue that we should treat a non-existing .stderr file as we would an | | empty file. I've opened !3121 fixing this. Hopefully you will see a | more | | helpful error message with this patch. | | | | Cheers, | | | | - Ben