James <[email protected]> writes: > On 01/05/15 10:28, David Kastrup wrote: >> David Kastrup <[email protected]> writes: >> >>> "Phil Holmes" <[email protected]> writes: >>> >>>> ----- Original Message ----- >>>> From: "David Kastrup" <[email protected]> >>>> To: <[email protected]> >>>> Sent: Friday, May 01, 2015 9:47 AM >>>> Subject: Strange "make check" error >>>> >>>> >>>>> Never seen anything like that. I suppose it will be a fluke and >>>>> rerunning the test will "fix" it, but has anybody encountered anything >>>>> like that? Strange bugout in the middle of the image comparisons? >>>>> >>>>> -- >>>>> David Kastrup >>>> >>>> Not seen it myself. Possibly a race condition or somesuch? >>>> >>>> Interesting that it was on output-distance, which is pretty much >>>> guaranteed to show a difference. >>> Oh superb. Reproducible. >> Well, could also be that my baseline is broken. So need to redo from >> full scratch. >> > Are you using Patchy and have you been using Patchy for different > patches recently? I sometimes get odd assertions all the time when > running a number of different patches one after another, even though > patchy is supposed to use make clean (or whatever it does) after each > test has completed. > > I can usually smell when something isn't right or looks odd and find > that the baseline or even the initial test-master / test-staging > branches that patchy uses are 'broken'; so I git branch -D both those > test-* branches, cat /dev/null >~/.lilypond-patchy-cache (which > removes any cruft that is probably overkill) and rm -rf /tmp/*lily* in > case the place that patchy puts the test branches to run the test are > poisoned. > > and then re-run ./test-patches.py and that usually helps.
Cleaned everything out. Baseline got rebuilt, same error. Checking different patch (4360 instead of 4357), same error. I'll eventually do the "reboot computer" dance but I suspect that we got ourselves a problem with Ubuntu 15.04. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
