The fail in gvfs/1.50.2-2 (ppc64el) is a common flaky case, it had hit systemd, glib2.0 and others before.
Example: AssertionError: Items in the first set but not the second: 'hello_gvfs_tests.2.txt'
Furthermore the breakage isn't related to the changes we applied. Retries should fix this, scheduling them ...
The fail in libsoup3/3.2.0-1 (armhf) This is another flaky case, having hit systemd before two times a few weeks ago.
Example:
# Apache command: '/usr/sbin/apache2' '-d' '/usr/libexec/installed-tests/libsoup-3.0' '-f' 'httpd.conf' '-c' 'ErrorLog /tmp/test-tmp-libsoup-3.0_connection-test.test-H7US21/error.log' '-c' 'PidFile /tmp/test-tmp-libsoup-3.0_connection-test.test-H7US21/httpd.pid' '-k' 'start' (98)Address already in use: AH00072: make_sock: could not bind to address 127.0.0.1:47526 no listening sockets available, shutting down ... FAIL: libsoup-3.0/connection-test.test (Child process exited with code 1)
I'll be retrying both
The fail in gvfs/1.50.2-2 (ppc64el) is a common flaky case, it had hit systemd, glib2.0 and others before.
Example: gvfs_tests. 2.txt'
AssertionError: Items in the first set but not the second:
'hello_
Furthermore the breakage isn't related to the changes we applied. Retries should fix this, scheduling them ...
The fail in libsoup3/3.2.0-1 (armhf)
This is another flaky case, having hit systemd before two times a few weeks ago.
Example:
# Apache command: '/usr/sbin/apache2' '-d' '/usr/libexec/ installed- tests/libsoup- 3.0' '-f' 'httpd.conf' '-c' 'ErrorLog /tmp/test- tmp-libsoup- 3.0_connection- test.test- H7US21/ error.log' '-c' 'PidFile /tmp/test- tmp-libsoup- 3.0_connection- test.test- H7US21/ httpd.pid' '-k' 'start' 3.0/connection- test.test (Child process exited with code 1)
(98)Address already in use: AH00072: make_sock: could not bind to address 127.0.0.1:47526
no listening sockets available, shutting down
...
FAIL: libsoup-
I'll be retrying both