[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cannot make test-baseline on current master
From: |
Jonas Hahnfeld |
Subject: |
Re: cannot make test-baseline on current master |
Date: |
Sat, 11 Jul 2020 12:01:31 +0200 |
User-agent: |
Evolution 3.36.4 |
Am Samstag, den 11.07.2020, 10:56 +0100 schrieb James Lowe:
> Hello,
>
> It seems on current master I get an error when trying to make test-basline
>
>
> I *can* make test-baseline on this commit.
>
> --snip--
>
> Author: Jonas Hahnfeld <hahnjo@hahnjo.de> 2020-06-29 13:16:51
> Committer: Jonas Hahnfeld <hahnjo@hahnjo.de> 2020-07-10 11:06:33
> Parent: bc38b9308ac82a72e67d971e0a15146cb3b2d625 (aclocal: use include
> for the in-place build too)
> Branches: master, remotes/origin/dev/hanwen/website,
> remotes/origin/dev/hanwen/xref-incdir, remotes/origin/dev/wl/fix-index,
> remotes/origin/master
> Follows: release/2.21.2-1
> Precedes:
>
> ci: Remove unneeded files from build artifacts
>
> --snip--
>
> So somewhere between then and now.
>
> I'll run through each commit to see if I can find the one that breaks it
> for me.
My guess would be
commit 075cc8c1f67e34465af8b8ca674daee73cdcf88c
Author: Han-Wen Nienhuys <hanwenn@gmail.com>
Date: Sun Jul 5 11:11:42 2020 +0200
Inline lilypond-book rules into regtest dir
The easiest solution (and something I've been planning to do...) is
removing the line
$(MAKE) out=test -C input/regression/lilypond-book local-test-baseline
from GNUmakefile.in's test-baseline. We're not comparing the baseline
of lilypond-book anyhow, so that's no loss. I'll try to submit a patch
later (and merge it directly if nobody objects and everything appears
to "just work" (tm)).
Jonas
signature.asc
Description: This is a digitally signed message part