T13615 fragile?

Alp Mestanogullari alp at well-typed.com
Wed Oct 9 08:53:12 UTC 2019

For what it's worth, I found two recent tickets documenting failures for 
that very same test: #16897 and #17269.

On 09/10/2019 10:45, Richard Eisenberg wrote:
> Hi devs,
> https://gitlab.haskell.org/rae/ghc/-/jobs/173504 tells me that T13615 
> failed -- but only in DEBUG mode. My patch is nowhere near this code. 
> Is this a new fragile test?
> The number of fragile tests seems to be growing quickly. And once a 
> test is labeled fragile, we're essentially no longer tracking the 
> test, if I understand correctly. So that's a bit unfortunate.
> Thanks,
> Richard
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Alp Mestanogullari, Haskell Consultant
Well-Typed LLP, https://www.well-typed.com/

Registered in England and Wales, OC335890
118 Wymering Mansions, Wymering Road, London, W9 2NF, England

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20191009/ee10c51d/attachment.html>

More information about the ghc-devs mailing list