On Mon, Jan 27, 2020 at 1:25 PM Ubuntu SRU Bot
<email address hidden> wrote:
>
> All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.22) for bionic have finished running.
> The following regressions have been reported in tests triggered by the package:
>
> systemd/237-3ubuntu10.33 (i386, s390x)
I was unable to reproduce this on a ppc64el instance. Since this test
depends on data from a remote source, I suspect something was out of
sync at the time. I retried the test and it passed.
On Mon, Jan 27, 2020 at 1:25 PM Ubuntu SRU Bot dfsg-1ubuntu7. 22) for bionic have finished running. 237-3ubuntu10. 33 (i386, s390x)
<email address hidden> wrote:
>
> All autopkgtests for the newly accepted qemu (1:2.11+
> The following regressions have been reported in tests triggered by the package:
>
> systemd/
Since this failure, a subsequent systemd/s390x test ran and passed /github. com/systemd/ systemd/ issues/ 8880
suggesting this is a flaky test. It looks like this bug:
https:/
The i386 failure looks like: /bugs.launchpad .net/ubuntu/ +source/ systemd/ +bug/1776654
https:/
I've therefore added a bionic task for it (as well as a theory on the
root cause). I did not retry this test.
> vagrant- mutate/ 1.2.0-3 (ppc64el)
I was unable to reproduce this on a ppc64el instance. Since this test
depends on data from a remote source, I suspect something was out of
sync at the time. I retried the test and it passed.
-dann