Exception: {'error': 'notify_push timed out'} via rpc_invoke()

[Bryce Harrington]

I get an error when pushing a branch up to my git-based project's repository:

$ git push origin testbed-setup-failures-are-bad
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
remote: Traceback (most recent call last):
remote: File "hooks/post-receive", line 227, in <module>
remote: rpc_invoke(
remote: File "hooks/post-receive", line 153, in rpc_invoke
remote: raise Exception(res)
remote: Exception: {'error': 'notify_push timed out'}
To git+ssh://git.launchpad.net/ppa-dev-tools
 * [new branch] testbed-setup-failures-are-bad -> testbed-setup-failures-are-bad

This gives a similar error message as LP: #2029135, although that one involved pack_count and was fixed some time ago, whereas this is an rpc_invoke() call.

I tried renaming the branch and pushing, in case something glitched with the first attempt, but I got the same error.

The main thing that's changed recently with my git repository, is that I enabled automatic snap builds. I don't remember if that was before or after my previously pushed branch but suspect it may be after. I wonder if the rpc_invoke() call is trying to kick off the snap build, maybe?

[Bryce Harrington (bryce)]

Seems to be working now. If someone fixed it, thank you!

$ git push -f origin testbed-setup-failures-are-bad
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 12 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 582 bytes | 582.00 KiB/s, done.
Total 4 (delta 3), reused 0 (delta 0), pack-reused 0
remote:
remote: Create a merge proposal for 'testbed-setup-failures-are-bad' on Launchpad by visiting:
remote: https://code.launchpad.net/~bryce/ppa-dev-tools/+git/ppa-dev-tools-1/+ref/testbed-setup-failures-are-bad/+register-merge
remote:
To git+ssh://git.launchpad.net/ppa-dev-tools
 + 93160d5...0c5c395 testbed-setup-failures-are-bad -> testbed-setup-failures-are-bad (forced update)

[Guruprasad (lgp171188)]

Hi Bryce, there were some infrastructure issues on the day you had this issue that should have caused the error that you encountered. It has been fixed on the same day and I can see that you have already gotten your push to work. Marking this bug as resolved.