This is non-exhaustive list of errors that can be reported by Patchmetrics, wither during its cronjobs or during normal operation.

Errors

Error: fatal: Invalid revision range ...

The complete error, usually reported by the cronjob update-committed-patches.py, might look like this:

fatal: Invalid revision range 4a2c44c8806f15d53b26f151139d878140609413..HEAD
Project lm-sensors: Error retrieving revisions list.
Last commit seen: 4a2c44c8806f15d53b26f151139d878140609413

It will report the name of the project (lm-sensors in the above example)

What to do in this case:

  • Make sure the git checkout directory is OK, run: git status. If there are changes, it is necessary to revert the repository and perform a pull again. Something like:

    git revert --hard HEAD~40 && git pull
  • Make sure all files are chmod-ed as www-data:www-data:

    chmod -R www-data:www-data *
  • From the admin interface, under Projects, click on the project that has the error, and reset the "Last seen commit ref" field. Here it is possible to set it empty, and Patchmetrics will rescan 20000 commit, or to set to a known hash value in the past from where to start the scan. Which hash to choose is up to you, a commit from a month in the past is usually a good idea (the output of git log is OK, and it will contain the hash to use).

Error: Timeout when performing git operation on...

The complete error, usually reported by the cronjob update-committed-patches.py, might look like this:

Timeout when performing git operation on 'linux-omap' (linux-omap).
 Project path: /tmp/linux-omap
 Project tree: git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
 Killing processes ['19354', '19355'] and moving on. Output of the kill command: (, ).

Usually this is a temporary problem and it disappears with the next run of the cronjob. If you see this error often for the same repository, it might be a good idea to:

  • Change the clone/pull URL and not use a dumb-HTTP one.

  • Manually clone the repository on the server, at the correct location.

What to do in this case:

  • Make sure the git checkout directory is OK, run: git status. If there are changes, it is necessary to revert the repository and perform a pull again. Something like:

    git revert --hard HEAD~40 && git pull
  • Try to run a git pull on the repository to fetch the latest changes.

  • Make sure all files are chmod-ed as www-data:www-data:

    chmod -R www-data:www-data *
  • From the admin interface check that the project git clone URL is correct.

Generic errors from Crowd

These kind of errors can be due to various reasons:

  • Crowd server not responding
  • Wrong email address used from an user to authenticate

In these cases it is necessary to investigate what caused the problem.

Platform/Systems/PathmetricsErrors (last modified 2014-06-24 17:47:30)