[Top][All Lists]

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

Re: 2.13.40 regtests

From: Phil Holmes
Subject: Re: 2.13.40 regtests
Date: Thu, 25 Nov 2010 17:45:36 -0000

"Neil Puttock" <address@hidden> wrote in message news:address@hidden
On 24 November 2010 15:47, Phil Holmes <address@hidden> wrote:

> So if a completely new bit of graphics appears, the regtest checker > wouldn't
> spot it? Not sure that's too good.

It might not, depending on whether the new grob influences bounding
boxes for other grobs.

> What's the checker written in?

Python: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob;f=scripts/build/output-distance.py


It wouldn't take me long to write a C# program (less than a day, I'd guess) that reproduced quite a lot of the regtest checker functionality and did a pixel-by-pixel check for image changes. I've done the latter bit in about 20 minutes on the figured bass png that started this discussion. The difference file it produces is attached. I'd be quite happy to do this, but wouldn't do it if it was felt to be stepping on other toes. I don't know python well enough to try looking at the existing file. I realise this couldn't be run as part of the build process, since it's windows only, but I'd be happy to run it locally and when I shuffle off the coil others _could_ do the same.

Not suggesting replacing the current checker - adding to it.

Phil Holmes
Bug Squad

Attachment: figured-bass-continuation-forbid.diffs.png
Description: PNG image

reply via email to

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