For some reason the cockpit tests time out when building on ppc64 http://ppc.koji.fedoraproject.org/koji/packageinfo?packageID=17615 PASS: test-sshtransport 4 /ssh-transport/close-problem PASS: test-sshtransport 5 /ssh-transport/terminate-problem PASS: test-transport 23 /transport/echo-large/child PASS: test-sshtransport 6 /ssh-transport/unsupported-auth PASS: test-sshtransport 7 /ssh-transport/auth-failed Identity added: /builddir/build/BUILD/cockpit-0.78/test_rsa_key (/builddir/build/BUILD/cockpit-0.78/test_rsa_key) cockpit-protocol-Message: 127.0.0.1: couldn't key authenticate: Bad authentication reply message type: 201326592 ** cockpit-protocol:ERROR:src/ws/test-sshtransport.c:285:on_closed_set_flag: assertion failed (problem == NULL): ("internal-error" == NULL) ./test-sshtransport terminated with SIGABRT FAIL: test-sshtransport 8 /ssh-transport/key-auth-message (process:52427): mock-agent-bridge-WARNING **: bridge couldn't spawn agent Child process exited with code 1: bind: Address already in use unix_listener: cannot bind to path: /builddir/build/BUILD/cockpit-0.78/test-agent.sock PASS: test-webservice 9 /web-service/kill-group PASS: test-auth 5 /auth/idle-timeout PASS: test-transport 24 /transport/echo-large/no-child PASS: test-transport 25 /transport/close-problem/child PASS: test-transport 26 /transport/close-problem/no-child PASS: test-webservice 10 /web-service/kill-host PASS: test-webservice 11 /web-service/specified-creds PASS: test-webservice 12 /web-service/specified-creds-fail PASS: test-auth 6 /auth/process-timeout PASS: test-webservice 13 /web-service/timeout-session PASS: test-webservice 14 /web-service/idling-signal PASS: test-webservice 15 /web-service/force-dispose PASS: test-webservice 16 /web-service/logout PASS: test-webservice 17 /web-service/handshake-and-auth/rfc6455 PASS: test-webservice 18 /web-service/handshake-and-auth/hixie76 PASS: test-webservice 19 /web-service/echo-message/rfc6455 PASS: test-webservice 20 /web-service/echo-message/hixie76 WebSocket-Message: connection unexpectedly closed by peer WebSocket-Message: connection unexpectedly closed by peer PASS: test-webservice 21 /web-service/echo-message/large PASS: test-webservice 22 /web-service/bad-origin/rfc6455 PASS: test-webservice 23 /web-service/bad-origin/hixie76 PASS: test-webservice 24 /web-service/bad-origin/withallowed PASS: test-webservice 25 /web-service/allowed-origin/rfc6455 PASS: test-webservice 26 /web-service/allowed-origin/hixie76 /bin/sh: /nonexistant: No such file or directory PASS: test-webservice 27 /web-service/fail-spawn/rfc6455 /bin/sh: /nonexistant: No such file or directory PASS: test-webservice 28 /web-service/fail-spawn/hixie76 PASS: test-webservice 29 /web-service/resource/simple PASS: test-webservice 30 /web-service/resource/not-found PASS: test-webservice 31 /web-service/resource/no-path PASS: test-webservice 32 /web-service/resource/failure PASS: test-webservice 33 /web-service/resource/checksum PASS: test-webservice 34 /web-service/resource/redirect-checksum PASS: test-webservice 35 /web-service/resource/not-modified PASS: test-webservice 36 /web-service/resource/no-checksum PASS: test-webservice 37 /web-service/resource/bad-checksum PASS: test-webservice 38 /web-service/resource/language-suffix PASS: test-webservice 39 /web-service/resource/language-fallback PASS: test-webservice 40 /web-service/resource/gzip-encoding EXCEPTION: Timeout(86400) expired for command: # bash --login -c /usr/bin/rpmbuild -bb --target ppc64 --nodeps /builddir/build/SPECS/cockpit.spec Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 84, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 487, in do raise commandTimeoutExpired("Timeout(%s) expired for command:\n # %s\n%s" % (timeout, command, output)) commandTimeoutExpired: Timeout(86400) expired for command: # bash --login -c /usr/bin/rpmbuild -bb --target ppc64 --nodeps /builddir/build/SPECS/cockpit.spec LEAVE do --> EXCEPTION RAISED
Seems it was a bug with libssh *** This bug has been marked as a duplicate of bug 1271230 ***