Re: regtests for previous stables failing

[Thomas Morley]

2017-10-27 8:21 GMT+02:00 David Kastrup <address@hidden>:
> Thomas Morley <address@hidden> writes:
>
>> 2017-10-26 23:26 GMT+02:00 David Kastrup <address@hidden>:
>>
>>> make clean
>>>
>>> before calling autogen.sh .
>>>
>>> Possibly make distclean .
>>
>> Being at lilypond-git/build (dev/2-18-test) I did:
>>
>> make clean
>> make distclean
>> cd ..
>> rm -fr build
>> sh autogen.sh --noconfigure
>> mkdir -p build/
>> cd build/
>> ../configure
>> make -j5
>> make -j5 test-baseline
>> make -j5 check
>>
>>
>> With same failure.
>
> Ah, separate build directory.  Try "make distclean" in the top source
> directory itself in case you configured it accidentally at one time.
>
> There also is the possibility of
>
> git clean -x -f
>
> But that's rather radical.  You should not be storing any files of your
> own in the directory then because this will remove every file not
> checked out via git.  With -d in addition, unknown directories will also
> get removed.>
> --
> David Kastrup


I first tried the steel broom, i.e.
git clean -x -f -d
rm -fr build
sh autogen.sh --noconfigure
mkdir -p build/
cd build/
../configure
make -j5
make -j5 test-baseline
make check

Same failure as before.
Then a fresh cloned repository:

git clone git://git.sv.gnu.org/lilypond.git ~/lilypond-git-test
cd lilypond-git-test/
git branch -a
git checkout remotes/origin/stable/2.18
git checkout -b dev/steble-2-18-test
sh autogen.sh --noconfigure
mkdir -p build/
cd build/
../configure
make -j5
make -j5 test-baseline
make -j5 check

Same failure as before.

Thoughts?

Thanks,
  Harm