I'm sorry to contribute to your frustration. I can see what the process _is_,
but my question (which I direct to LilyPond developers in general) is whether
it is _justified_ that `make check` run to completion using an out-of-date
`lilypond` rather than either rebuilding it first or raising some kind of
alarm. Must we continue to put up with it?
The purpose of `make` is to follow dependencies and do exactly what needs to be
done. The difference in behavior between these cases seems contrary to that:
* `make && make check`
* `make check`
---
** [issues:#5564] Fix conversion warnings in beaming code**
**Status:** Started
**Created:** Wed Oct 02, 2019 02:50 AM UTC by Dan Eble
**Last Updated:** Thu Oct 10, 2019 01:47 PM UTC
**Owner:** pkx166h
Fix conversion warnings in beaming code
Changes include preserving sizes and indices as vsize types and adding
explicit static casts. Warnings were reported by g++ 9.2.1 on x86_64.
http://codereview.appspot.com/553010043
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
