update-committed-patches.py locks up

[Ben Copeland]

First noticed that commits were not being updated. Upon looking into why I noticed the lock file was stuck. I deleted the lock file and ran the script in a screen. I noticed that the script was getting stuck, on a guess at newlib.

I can copy and paste what was outputted, but I'm not sure if this is the reason why it got stuck.

I am running the script again to see if it gets stuck at the same spot.

M net/wireless/wext-compat.c
M net/wireless/wext-sme.c

 stderr: Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.

fatal: Invalid revision range 3983cdf5d68523032830e580433cca6358000261..HEAD
fatal: http://git.infradead.org/users/dedekind/l2-mtd.git/info/refs not valid: is this a git repository?
Failed to fetch http://git.infradead.org/users/dedekind/l2-mtd.git (linux-mtd - linux-mtd).
 stdout: Cloning into '/tmp/linux-mtd'...

 stderr: None

And in the update-comitted-patches.log:

================================================================================

================================================================================
Scanning commits of newlib

[Milo Casagrande (milo)]

I re-run the script manually on the staging instance and found out that it does not really lock there doing nothing.
When patches scans a repository for the first time, it can scan something like 20k commits. With a medium sized repository this can take hours, since it also depends on the size of the commit that it is scanning.