Re: [Lilypond-auto] Issue 3500 in lilypond: Patchy apparently fails to clean up after tests, leading to interdependencies and failures

[lilypond]

Comment #3 on issue 3500 by address@hidden: Patchy apparently fails  
to clean up after tests, leading to interdependencies and failures
http://code.google.com/p/lilypond/issues/detail?id=3500

This is actually something that is being done, as well, before applying any  
patch:  
https://github.com/gperciva/lilypond-extra/blob/master/patches/compile_lilypond_test/__init__.py#L297

The use of "run" in that code instead of "self.runner" means that those  
commands are not being logged. Is it possible that they sometimes fail?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings