Keith OHara <k-ohara5...@oco.net> writes: > Federico Bruni <fedelogy <at> gmail.com> writes: > >> Il giorno ven 26 dic 2014 alle 23:32, Trevor Daniels >> <t.daniels <at> treda.co.uk> ha scritto: >> > >> > Was this regtest never executed before being committed?! >> >> Well, at least by the automatic doc build: >> https://code.google.com/p/lilypond/issues/detail?id=4176#c2 >> >> It seems that it doesn't occur in any situation: >> http://lists.gnu.org/archive/html/bug-lilypond/2014-10/msg00071.html >> > > It seems that we knew about these problems, bug then added the > regression tests anyway. > > We have bug-reports, so it seems we lose no information
Bug reports or an actual issue in the tracker? > if we avoid these issues in the regression test, but the last time I > tried that I got > <http://lists.gnu.org/archive/html/lilypond-devel/2011-11/msg00559.html> There was no attempt of even making a tracker issue that time as far as I can tell, it was strictly a sweep-under-the-rug approach. I consider it reasonable to reduce a regtest to trigger the issue it is intended for, but if it shows an unrelated problem, we should not remove it without creating an issue report for it. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond