[Top][All Lists]

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

Re: GSoC 2020: Unexpected "regressions"...

From: Michael Käppler
Subject: Re: GSoC 2020: Unexpected "regressions"...
Date: Fri, 28 Aug 2020 12:00:08 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

Am 28.08.2020 um 09:53 schrieb Michael Käppler:
Am 28.08.2020 um 09:03 schrieb Owen Lamb:
Hi all,

I've encountered a couple of unexpected regressions for my first commit.
The first one was an issue with tablature stems, which I was able to
The other, however, is baffling to me.

It appears that musicxml2ly creates slightly different .ly files between
the two commits, for musicxml tests 03b and 71d. In particular, it's
confusing the order of two voices within a staff. The odd thing is that
test 71d appears to have correct output only *after *my commit is
while 03b is correct only *before *my commit is applied (i.e. on the
baseline commit).

None of my code did a thing to musicxml, so I'm utterly confused. Is
some inconsistency with musicxml2ly that may have caused this

I'd appreciate it if anyone has time to do a regression test on their
machine, just to make sure it's not just a problem with my system. I was
comparing f93efe2a (baseline, last commit before mine) and 8df138ae (my
first commit).
Will run the tests on my machine today and report the results to the
list ASAP.
I cannot reproduce this on my machine.
What I see are differences in input/regression/
(which I would describe as slightly different spacing)
and input/regression/, where
some glyph is missing.
The log file says

warning: Cannot find glyph noteheads.u2do


reply via email to

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