lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make test


From: Julien Rioux
Subject: Re: make test
Date: Tue, 21 Aug 2012 13:19:50 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0

On 08/08/2012 4:59 AM, Phil Holmes wrote:
I've been looking at how the regression test comparison works.  The
first thing I find is that we have 2 effectively duplicate, but
different, pages on running regtest comparisons:

http://lilypond.org/doc/v2.15/Documentation/contributor/verify-regression-tests

http://lilypond.org/doc/v2.15/Documentation/contributor/regtest-comparison

I think the latter is probably more accurate.  I think it would be best
to delete one and point to the other?

I've also been benchmarking.  For example, I know that make CPU_COUNT=9
test is _much_ faster than make test, but the make -j9 test isn't worth
doing - most of the time is spent building the single regtest document,
which lilypond parallelises much better than make.  I have had errors
using -jX so am slightly suspicious of that option.  I would like to add
the best way to parallelise the test process to the CG.


Currently the build system is set up so that all regtests in a given directory are processed by one instance of lilypond (called from lilypond-book). Since there is only one process, there really isn't anything that `make' could parallelize in this area. At the same time, there's nothing to fear in using -j9 to make test.

I've also been looking at how output-distance works.  Does anyone now
understand what this actually does?  From following the code, it looks
to me like it doesn't actually compare images - it compares the
.signature files, and if there's a difference over the threshold, it
creates an image of the original and changed file, and then makes a
"ghost" version of the change to overlay on the original.  Does this
seem correct.  Worth documenting?

--
Phil Holmes


--
Julien




reply via email to

[Prev in Thread] Current Thread [Next in Thread]