On 07/01/2020 07:36, Brian May wrote: > Brian May <b...@debian.org> writes: > >> My build is still running the tests, but I don't expect any problems as >> the test was getting skipped anyway... > > Tests seem to be hanging, on the next test after: > > PASS: network-address 37 /gresolver/resolve-address/0 > PASS: network-address 38 /gresolver/resolve-address/1 > PASS: network-address 39 /gresolver/resolve-address/2 > PASS: network-address 40 /gresolver/resolve-address/3 > PASS: network-address 41 /gresolver/resolve-address/4 > PASS: network-address 42 /gresolver/resolve-address/5 > PASS: network-address 43 /gresolver/resolve-address/6 > PASS: network-address 44 /gresolver/resolve-address/7 > PASS: network-address 45 /gresolver/resolve-address/8 > PASS: network-address 46 /gresolver/resolve-address/9 > PASS: network-address 47 /gresolver/resolve-address/10 > PASS: network-address 48 /gresolver/resolve-address/11 > PASS: network-address 49 /gresolver/resolve-address/12 > > Running Command seems to be: > > /bin/bash /build/glib2.0-S2dcj2/glib2.0-2.42.1/./tap-driver.sh > --test-name network-monitor --log-file network-monitor.log --trs-file > network-monitor.trs --color-tests no --enable-hard-errors yes > --expect-failure no -- /build/glib2.0-S2dcj2/glib2.0-2.42.1/./tap-test > ./network-monitor > > This doesn't appear to be anything related to anything I have changed. > Will try building again without my patches.
Yes, that's the failing test I mentioned in my email. Building without the patches works for me. I am still looking at whether upgrading ibus is worth it due to the regression risk. Cheers, Emilio
