lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 3500 in lilypond: Patchy apparently fails to c


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3500 in lilypond: Patchy apparently fails to clean up after tests, leading to interdependencies and failures
Date: Fri, 16 Aug 2013 10:42:25 +0000


Comment #1 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

Although the log does not report it, "git reset --hard" is used right after "make clean".

In https://github.com/gperciva/lilypond-extra/blob/master/patches/compile_lilypond_test/__init__.py#L281 you'll see that the sequence is "make test-clean", "make doc-clean" (if necessary), "make clean", then the patch_issue.unapply_patch_commands are run, which are defined at https://github.com/gperciva/lilypond-extra/blob/master/patches/projecthosting_patches.py#L56 to use "git reset --hard".

If there is an interdependent failure here, it comes from somewhere else we're missing.

--
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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]