I've stopped validating locally, allowing Travis to do it for me. If you use a `wip/...` branch and push to the main GHC repo, you can find build reports at travis-ci.org/ghc/ghc. Or, I'm sure if you clue Travis in, this can also work if you push to your own GitHub fork of GHC.
Admittedly, this is a bad workflow if you're expecting a bunch of extraneous-import failures (and such) during validation, but I just wanted to make sure you knew of this option.
Richard
On Nov 8, 2014, at 7:50 PM, "Edward Z. Yang"
It does work, and it's very useful.
Edward
Excerpts from Thomas Miedema's message of 2014-11-08 14:35:27 -0800:
I was wondering how do other devs `validate` their tree? In particular, I just merged a whole bunch of stuff and am validating things. However, every time something goes wrong (e.g., unused import warning), the whole process starts from the beginning, which is quite time consuming.
$ ./validate --help ... --no-clean don't make clean first, just carry on from a previous interrupted validation run ...
I don't know if it works!
ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs