qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Richard Henderson <richard.henderson@linaro.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PULL 00/12] First batch of s390x patches for QEMU 8.2
Date: Thu, 24 Aug 2023 08:52:27 +0200	[thread overview]
Message-ID: <aee5829f-37a4-4169-1a70-8f9a40b4f45d@redhat.com> (raw)
In-Reply-To: <20230823163440.GA851545@fedora>

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




  reply	other threads:[~2023-08-24  6:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 11:45 [PULL 00/12] First batch of s390x patches for QEMU 8.2 Thomas Huth
2023-08-23 11:45 ` [PULL 01/12] hw: Add compat machines for 8.2 Thomas Huth
2023-08-23 11:45 ` [PULL 02/12] s390x: Convert DPRINTF to trace events Thomas Huth
2023-08-23 11:45 ` [PULL 03/12] target/s390x: Check reserved bits of VFMIN/VFMAX's M5 Thomas Huth
2023-08-23 11:45 ` [PULL 04/12] target/s390x: Fix VSTL with a large length Thomas Huth
2023-08-23 11:45 ` [PULL 05/12] tests/tcg/s390x: Test VSTL Thomas Huth
2023-08-23 11:45 ` [PULL 06/12] target/s390x: Use a 16-bit immediate in VREP Thomas Huth
2023-08-23 11:45 ` [PULL 07/12] tests/tcg/s390x: Test VREP Thomas Huth
2023-08-23 11:45 ` [PULL 08/12] hw/s390x/s390-virtio-ccw: Remove superfluous code to set the NIC model Thomas Huth
2023-08-23 11:45 ` [PULL 09/12] include/hw/virtio/virtio-gpu: Fix virtio-gpu with blob on big endian hosts Thomas Huth
2023-08-23 14:00   ` Michael Tokarev
2023-08-23 14:02     ` Thomas Huth
2023-08-23 14:03     ` Michael Tokarev
2023-08-23 11:45 ` [PULL 10/12] linux-user/elfload: Enable vxe2 on s390x Thomas Huth
2023-08-23 11:45 ` [PULL 11/12] target/s390x: Fix the "ignored match" case in VSTRS Thomas Huth
2023-08-23 11:45 ` [PULL 12/12] tests/tcg/s390x: Test VSTRS Thomas Huth
2023-08-23 13:19 ` [PULL 00/12] First batch of s390x patches for QEMU 8.2 Stefan Hajnoczi
2023-08-23 16:34 ` Stefan Hajnoczi
2023-08-24  6:52   ` Thomas Huth [this message]
2023-08-24 14:51     ` Stefan Hajnoczi
2023-08-24 16:10       ` Thomas Huth
2023-08-24 16:21         ` Peter Maydell
2023-08-25  4:51         ` Philippe Mathieu-Daudé

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aee5829f-37a4-4169-1a70-8f9a40b4f45d@redhat.com \
    --to=thuth@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).