[Python-Dev] test coverage summaries - now updated nightly

[Mark Hammond]

[Skip]

>     Mark> It would be great if there was some sort of "multi-platform"
>     Mark> support, and a merging of the results.

> Agreed.  We could set up a scheme where people run my scripts on other
> systems and then mail me the generated files.  Windows would be kind of
> tough though, because my stuff currently relies on gcc/gcov.  What
> facilities does Windows have for coverage testing Mark?

There is a source-profiler, but Im not sure how deep it lets you into the
data.  I'll look into this at some stage.

Or some people are working towards gcc makefiles for windows - maybe that
is a better way to go for this?


   Mark> Along the same vein is the Mozilla "tinderbox".  It
...

> That seems a bit extreme to me, and I don't know about you, but
> I don't have
> the spare resources available to "burn" on such a project.

I think that the tinderbox code is open-source too!  I agree this is a bit
extreme, but I do believe something like it would be useful, and need not
be too hard.  As more and more checkins happen from different people, the
chances of platform-breakage would seem to be quite high.

A Python script that periodically scanned CVS for changes, then executed a
build and did something pretty simple with the log wouldnt be too hard.

However, I do agree we should wait until it is _nearly_ a problem (as
opposed to _is_ a problem :-)

Mark.