On 28/08/2012 21:30, Johan Tibell wrote:
On Mon, Aug 27, 2012 at 11:21 PM, Simon Hengel <s...@typeful.net> wrote:
Hi,
we have several issues on Haddock's ghc-7.6 branch. I fixed some of
those, but some still persist.
Isolated, none of those issues are a big deal. But combined they are.
Is there a way we can prevent situations like this in the future? Would
it work to establish the convention that if you change Haddock you have
to build a vanilla Haddock (say without in-ghc-tree) and run the test
suite?
Is there a build bot that builds haddock and runs its tests on a
regular basis? That's the best way I know to keep things from
regressing without spending too much effort.
Right. GHC's validate already builds Haddock and runs that Haddock over
all the packages in the GHC tree. It shouldn't be hard to add the
Haddock test suite too. Paolo, maybe you could look into that?
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
