> Does the (bug?) report I sent get a ticket in
> https://gitlab.com/lilypond/lilypond/-/issues ?
Not yet, I was busy, sorry.
> I ran your suggested - "branch regression test":
> [@master, test-baseline, bytecode, @MyBranch, bytecode, check]
> Indeed lots of regtests failures.
>
> Another fix attempt is attached.
Thanks! Please submit a Merge Request, if possible; this allows other
people to have a look.
> If I knew how to debug Scheme code, I might have come with a finer
> solution.
Assuming you want to know the value of Scheme expression `foo`, you
might insert `(ly:message "foo: ~a" foo)` into the Scheme code to get
relevant output on the console. Then do `make bytecode`, then run
your test code. For playing around with LilyPond's Scheme engine you
might also try the sandbox:
```
rlwrap <build>/out/bin/lilypond scheme-sandbox
```
(Using the external `rlwrap` program makes working on the sandbox
command line *much* more comfortable.)
> To my surprise, also (attached)
> build/input/regression/midi/out/midi.diff Could it be that I missed
> something in the "branch regression test" ?
I don't know what's going on, sorry. But looking at the version diffs
(2.25.0 vs. 2.14.0) the problem seems to be elsewhere with running the
test suite, so for the moment, I believe, you can ignore those MIDI
tests.
Werner
