`devel2` compiles GHC with extra assertions and `./validate` doesn't
do that. There's `./validate --slow` that enables extra assertions.
AFAIK harbormaster (and most ghc-devs) only does `./validate` which
explains how failures like this can sneak in.
We used to have a travis build that did `./vali
In a freshly cloned GHC code base (c6462ab0...), in my system,`make test
TEST="T13780c T13822"` fails.
That is while `./validate` passes.
I am rather new to GHC code base, and not so familiar with its build and
testing system.
So I was wondering whether this is an intended behaviour (e.g., some te
