14.4.7 Troubleshooting Patchy

The following is a list of the most common messages that the scripts may report with explanations.

this Git revision has already been pushed by an operator other than this Patchy.

• Another, remote, machine has already tested and pushed the new commits in staging.
• You may also see this if the auto-build files have been deleted and this computer has previously already pushed the listed commit ID to master.

test-master-lock and PID entry exist but previous Patchy
run (PID xxxxx) died, resetting test-master-lock anyway.

A previous attempt was unsuccessful for some reason and the scripts were not able to tidy up after themselves (for example if you manually halt the process by killing it or closing the terminal you may have been running the script in). The test-master-lock branch was therefore not able to be deleted cleanly however, nothing needs to be done the scripts will rebuild any tests it needs to.

fatal: A branch named 'test-master-lock' already exists.

• There is another instance of Patchy running on your computer that is testing the same tracker issue.
• A previous test attempt was unsuccessful for some reason and the scripts were not able to tidy up after themselves (for example if you manually halt the testing process by killing it or closing the terminal you may have been running the script in). The test-master-lock branch was therefore not able to be deleted cleanly, in this case you must manually delete the test-master-lock branch in your $LILYPOND_GIT directory.

  git branch -d test-master-lock
  

  It may be wise to also manually delete test-master and test-staging too, just to be safe.

*** FAILED STEP ***
        merge from staging
        Another instance (PID xxxxx) is already running.

This occurs when trying to run lilypond-patchy-staging.py when another instance of either script is already running locally.

<< Back to Documentation Index

LilyPond — Contributor’s Guide v2.21.0 (development-branch).