Message ID | 20230823114544.216520-1-thuth@redhat.com |
---|---|
State | New |
Headers | show |
Applied, thanks. Please update the changelog at https://wiki.qemu.org/ChangeLog/8.2 for any user-visible changes.
On Wed, Aug 23, 2023 at 01:45:32PM +0200, Thomas Huth wrote: > The following changes since commit b0dd9a7d6dd15a6898e9c585b521e6bec79b25aa: > > Open 8.2 development tree (2023-08-22 07:14:07 -0700) > > are available in the Git repository at: > > https://gitlab.com/thuth/qemu.git tags/pull-request-2023-08-23 > > for you to fetch changes up to 6c49f685d30ffe81cfa47da2c258904ad28ac368: > > tests/tcg/s390x: Test VSTRS (2023-08-23 12:07:30 +0200) Hi Thomas, Please take a look at the following ubuntu-20.04-s390x-all CI failure: https://gitlab.com/qemu-project/qemu/-/jobs/4931341536 Stefan
On 23/08/2023 18.34, Stefan Hajnoczi wrote: > On Wed, Aug 23, 2023 at 01:45:32PM +0200, Thomas Huth wrote: >> The following changes since commit b0dd9a7d6dd15a6898e9c585b521e6bec79b25aa: >> >> Open 8.2 development tree (2023-08-22 07:14:07 -0700) >> >> are available in the Git repository at: >> >> https://gitlab.com/thuth/qemu.git tags/pull-request-2023-08-23 >> >> for you to fetch changes up to 6c49f685d30ffe81cfa47da2c258904ad28ac368: >> >> tests/tcg/s390x: Test VSTRS (2023-08-23 12:07:30 +0200) > > Hi Thomas, > Please take a look at the following ubuntu-20.04-s390x-all CI failure: > https://gitlab.com/qemu-project/qemu/-/jobs/4931341536 It says: "TimeoutError: Timeout waiting for job to pause" ... could you please check the load on that host? ... I think that s390x runner is known for being too slow some times, so I assume that problem should go away if you re-run the job when it is less loaded. Thomas
On Thu, 24 Aug 2023 at 02:53, Thomas Huth <thuth@redhat.com> wrote: > > On 23/08/2023 18.34, Stefan Hajnoczi wrote: > > On Wed, Aug 23, 2023 at 01:45:32PM +0200, Thomas Huth wrote: > >> The following changes since commit b0dd9a7d6dd15a6898e9c585b521e6bec79b25aa: > >> > >> Open 8.2 development tree (2023-08-22 07:14:07 -0700) > >> > >> are available in the Git repository at: > >> > >> https://gitlab.com/thuth/qemu.git tags/pull-request-2023-08-23 > >> > >> for you to fetch changes up to 6c49f685d30ffe81cfa47da2c258904ad28ac368: > >> > >> tests/tcg/s390x: Test VSTRS (2023-08-23 12:07:30 +0200) > > > > Hi Thomas, > > Please take a look at the following ubuntu-20.04-s390x-all CI failure: > > https://gitlab.com/qemu-project/qemu/-/jobs/4931341536 > > It says: "TimeoutError: Timeout waiting for job to pause" ... could you > please check the load on that host? ... I think that s390x runner is known > for being too slow some times, so I assume that problem should go away if > you re-run the job when it is less loaded. I ran it again and it timed out. I've merged the PR and assume the test is just flaky. Stefan
On 24/08/2023 16.51, Stefan Hajnoczi wrote: > On Thu, 24 Aug 2023 at 02:53, Thomas Huth <thuth@redhat.com> wrote: >> >> On 23/08/2023 18.34, Stefan Hajnoczi wrote: >>> On Wed, Aug 23, 2023 at 01:45:32PM +0200, Thomas Huth wrote: >>>> The following changes since commit b0dd9a7d6dd15a6898e9c585b521e6bec79b25aa: >>>> >>>> Open 8.2 development tree (2023-08-22 07:14:07 -0700) >>>> >>>> are available in the Git repository at: >>>> >>>> https://gitlab.com/thuth/qemu.git tags/pull-request-2023-08-23 >>>> >>>> for you to fetch changes up to 6c49f685d30ffe81cfa47da2c258904ad28ac368: >>>> >>>> tests/tcg/s390x: Test VSTRS (2023-08-23 12:07:30 +0200) >>> >>> Hi Thomas, >>> Please take a look at the following ubuntu-20.04-s390x-all CI failure: >>> https://gitlab.com/qemu-project/qemu/-/jobs/4931341536 >> >> It says: "TimeoutError: Timeout waiting for job to pause" ... could you >> please check the load on that host? ... I think that s390x runner is known >> for being too slow some times, so I assume that problem should go away if >> you re-run the job when it is less loaded. > > I ran it again and it timed out. I've merged the PR and assume the > test is just flaky. I think someone needs to look at the runner to see whether there is still old stuff taking CPU time or something similar. At least the two issues that occurred with the initial run ( qtest-i386/migration-test and io-qcow2-041) didn't reproduce in the follow up run here: https://gitlab.com/qemu-project/qemu/-/pipelines/979072973 (the ahci-test was failing instead) Thomas
On Thu, 24 Aug 2023 at 17:10, Thomas Huth <thuth@redhat.com> wrote: > > On 24/08/2023 16.51, Stefan Hajnoczi wrote: > > On Thu, 24 Aug 2023 at 02:53, Thomas Huth <thuth@redhat.com> wrote: > >> > >> On 23/08/2023 18.34, Stefan Hajnoczi wrote: > >>> On Wed, Aug 23, 2023 at 01:45:32PM +0200, Thomas Huth wrote: > >>>> The following changes since commit b0dd9a7d6dd15a6898e9c585b521e6bec79b25aa: > >>>> > >>>> Open 8.2 development tree (2023-08-22 07:14:07 -0700) > >>>> > >>>> are available in the Git repository at: > >>>> > >>>> https://gitlab.com/thuth/qemu.git tags/pull-request-2023-08-23 > >>>> > >>>> for you to fetch changes up to 6c49f685d30ffe81cfa47da2c258904ad28ac368: > >>>> > >>>> tests/tcg/s390x: Test VSTRS (2023-08-23 12:07:30 +0200) > >>> > >>> Hi Thomas, > >>> Please take a look at the following ubuntu-20.04-s390x-all CI failure: > >>> https://gitlab.com/qemu-project/qemu/-/jobs/4931341536 > >> > >> It says: "TimeoutError: Timeout waiting for job to pause" ... could you > >> please check the load on that host? ... I think that s390x runner is known > >> for being too slow some times, so I assume that problem should go away if > >> you re-run the job when it is less loaded. > > > > I ran it again and it timed out. I've merged the PR and assume the > > test is just flaky. > > I think someone needs to look at the runner to see whether there is still > old stuff taking CPU time or something similar. It does not currently seem to be running anything it should not be. The uptime is less than 2 days so it was rebooted recently. thanks -- PMM
On 24/8/23 18:10, Thomas Huth wrote: > On 24/08/2023 16.51, Stefan Hajnoczi wrote: >> On Thu, 24 Aug 2023 at 02:53, Thomas Huth <thuth@redhat.com> wrote: >>> >>> On 23/08/2023 18.34, Stefan Hajnoczi wrote: >>>> On Wed, Aug 23, 2023 at 01:45:32PM +0200, Thomas Huth wrote: >>>>> The following changes since commit >>>>> b0dd9a7d6dd15a6898e9c585b521e6bec79b25aa: >>>>> >>>>> Open 8.2 development tree (2023-08-22 07:14:07 -0700) >>>>> >>>>> are available in the Git repository at: >>>>> >>>>> https://gitlab.com/thuth/qemu.git tags/pull-request-2023-08-23 >>>>> >>>>> for you to fetch changes up to >>>>> 6c49f685d30ffe81cfa47da2c258904ad28ac368: >>>>> >>>>> tests/tcg/s390x: Test VSTRS (2023-08-23 12:07:30 +0200) >>>> >>>> Hi Thomas, >>>> Please take a look at the following ubuntu-20.04-s390x-all CI failure: >>>> https://gitlab.com/qemu-project/qemu/-/jobs/4931341536 >>> >>> It says: "TimeoutError: Timeout waiting for job to pause" ... could you >>> please check the load on that host? ... I think that s390x runner is >>> known >>> for being too slow some times, so I assume that problem should go >>> away if >>> you re-run the job when it is less loaded. >> >> I ran it again and it timed out. I've merged the PR and assume the >> test is just flaky. > > I think someone needs to look at the runner to see whether there is > still old stuff taking CPU time or something similar. Would reporting the runner load on failure help in some way?