Re: Issue 1370 in lilypond: any console-output-producing regtests should be separate

[lilypond]

Comment #1 on issue 1370 by v.villenave: any console-output-producing  
regtests should be separate
http://code.google.com/p/lilypond/issues/detail?id=1370

Good idea! Here are a few regtests that may qualify (for various reasons):

apply-context.ly
automatic-polyphony-context-id.ly
backend-svg.ly
beam-quarter.ly
clef-warn.ly
clip-systems.ly
display-lily-tests.ly
general-scheme-bindings.ly
grace-end.ly
grace-end2.ly
graphviz.ly
harp-pedals.ly
harp-pedals-sanity-checks.ly
invalid-engraver.ly
markup-brace-warning.ly
markup-music-glyph.ly
option-help.ly
page-break-warn-forbidden.ly
paper-margins-overrun.ly
paper-margins-consistency.ly
profile-property-access.ly
safe.ly
test-output-distance.ly
to-xml.ly
warn-conflicting-key-signatures.ly
warn-unterminated-span-dynamic.ly
woodwind-diagrams-key-lists.ly