Comment 18 for bug 1647204

Sorry, I did a 2nd build as something odd happened in the arm64 builder of the 1st.

As you rightly say, they just hand now and will be killed by L.

Manually cancelling a build reveals some more about what what happening at the time. see below:

This agree with other diagnostic builds I did which show the hanging call is

c.op_genkey(parms, None, None)

---------- Log from manually cancelled build ------------

GNUPGHOME=/<<PKGBUILDDIR>>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \
  --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \
  initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
starting gpg-agent
RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['scan-for-processes', 'PACKAGEBUILD-11850388']
Scanning for processes to kill in build /home/buildd/build-PACKAGEBUILD-11850388/chroot-autobuild...
Traceback (most recent call last):
  File "./t-callbacks.py", line 105, in <module>
    c.op_genkey(parms, None, None)
  File "/<<PKGBUILDDIR>>/lang/python/build/lib.linux-x86_64-2.7/gpg/core.py", line 151, in wrapper
    return _funcwrap(self, *args)
  File "/<<PKGBUILDDIR>>/lang/python/build/lib.linux-x86_64-2.7/gpg/core.py", line 135, in _funcwrap
    return errorcheck(result, "Invocation of " + name)
  File "/<<PKGBUILDDIR>>/lang/python/build/lib.linux-x86_64-2.7/gpg/errors.py", line 62, in errorcheck
    raise GPGMEError(retval, extradata)
gpg.errors.GPGMEError: Invocation of gpgme_op_genkey: GnuPG: End of file