|
From: | James |
Subject: | Re: Strange "make check" error |
Date: | Fri, 01 May 2015 11:44:49 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
On 01/05/15 11:40, David Kastrup wrote:
David Kastrup <address@hidden> writes: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.Well, either that, or with the latest changes in master. But they should have passed through some instance of Patchy too after all. Or doesn't the staging patchy do a "make check"? Perhaps it only does "make test"? Because it is "make check" that appears to be newly broken.
Patchy staging doesn't do the make check but it does do all the others including make doc
--snip-- From ssh://git.sv.gnu.org/srv/git/lilypond 8dd74d9..e108145 staging -> origin/staging Merged staging, now at: e1081454de4c8167f3f010912de061822226f61d Success: ./autogen.sh --noconfigure Success: /tmp/lilypond-autobuild/configure --disable-optimising Success: nice make clean Success: nice make -j6 CPU_COUNT=6 Success: nice make test -j6 CPU_COUNT=6 Success: nice make doc -j6 CPU_COUNT=6 To ssh://address@hidden/srv/git/lilypond.git 8dd74d9..e108145 test-staging -> master Success: pushed to master --snip--
[Prev in Thread] | Current Thread | [Next in Thread] |