If I'm reading the "update excuses" output correctly, this package update is blocked by autopkgtest failures:
[...]
ok 14 /tls/connection/simultaneous-sync
**
GLib-Net:ERROR:connection.c:368:run_echo_server: assertion failed (error == NULL): Error performing TLS handshake: The specified session has been invalidated for some reason. (g-tls-error-quark, 1)
# GLib-Net:ERROR:connection.c:368:run_echo_server: assertion failed (error == NULL): Error performing TLS handshake: The specified session has been invalidated for some reason. (g-tls-error-quark, 1)
Test glib-networking/connection.test failed: Child process killed by signal 6
Running test: /usr/share/installed-tests/glib-networking/file-database.test
[...]
Since the failures are specifically about TLS handshake failures, it feels unlikely to be transient test failures. Someone needs to investigate this further.
If I'm reading the "update excuses" output correctly, this package update is blocked by autopkgtest failures:
[...] /simultaneous- sync ERROR:connectio n.c:368: run_echo_ server: assertion failed (error == NULL): Error performing TLS handshake: The specified session has been invalidated for some reason. (g-tls-error-quark, 1) ERROR:connectio n.c:368: run_echo_ server: assertion failed (error == NULL): Error performing TLS handshake: The specified session has been invalidated for some reason. (g-tls-error-quark, 1) /connection. test failed: Child process killed by signal 6 installed- tests/glib- networking/ file-database. test
ok 14 /tls/connection
**
GLib-Net:
# GLib-Net:
Test glib-networking
Running test: /usr/share/
[...]
That's from https:/ /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- trusty/ trusty/ ppc64el/ g/glib- networking/ 20170818_ 000323_ c2d95@/ log.gz
It looks like none of the architectures for glib-networking succeeded:
http:// people. canonical. com/~ubuntu- archive/ proposed- migration/ trusty/ update_ excuses. html#gnutls26
Since the failures are specifically about TLS handshake failures, it feels unlikely to be transient test failures. Someone needs to investigate this further.
Thanks