[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < Automating Patchy ]		[  Up : Automated testing with Patchy ]	[ Administrative mailing list > ]

14.4.7 Troubleshooting Patchy

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

• issues []
  

  • There are currently no tracker issues with the Patch-New status.
  • If specific tracker issue number has been used as an argument when running test-patches.py, then the issue contains no URL to Rietveld.

• 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 on your local machine if the auto-build files have been deleted and this computer has previously already pushed the listed commit ID to master.

• Git revision has not changed but checksum of test baseline has, must rebuild.

  This occurs when Patchy detects that the commit ID has not changed since the last test but it cannot locate the last make test-baseline (usually because it has been deleted or moved) and so a new test-baseline is rebuilt.

• Last patch for issue xxxx already tested or under testing
  by another Patchy instance, skipping.
  

  • 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).

    There is a hidden file located in the $HOME directory of the user running Patchy called .lilypond-patchy-cache that records the current patches that are being tested, have been tested and the commit ID of remote/origin/master since the last test. It will contain a line like this:

    [3995]
    issue105560044_120001_diff = testing
    

    for any issue that it thinks is still in the process of being tested.

    Manually remove this entry and re-run the script.

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

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

• Warning: something went wrong; omitting patch for issue 3976
  

  • The Rietveld URL as listed in the tracker is incorrect (e.g. missing or incorrect issue number
  • The patch on Rietveld is too large to download

---

[ << Administrative policies ]	[Top][Contents][Index][ ? ]			[ LilyPond grammar >> ]
[ < Automating Patchy ]		[  Up : Automated testing with Patchy ]	[ Administrative mailing list > ]

<< Back to Documentation Index

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