qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Ulrich Weigand" <ulrich.weigand@de.ibm.com>
Subject: Re: [RFC] gitlab: introduce s390x wasmtime job
Date: Tue, 05 Jul 2022 22:41:50 +0200	[thread overview]
Message-ID: <ad7a0620ca3279ab857050b2850f3e1e330539c7.camel@linux.ibm.com> (raw)
In-Reply-To: <CAFEAcA_Twju4rnn0f97nEshorwbaDK2n0vcdMXDWcwuuguikzQ@mail.gmail.com>

On Tue, 2022-07-05 at 15:40 +0100, Peter Maydell wrote:
> On Tue, 5 Jul 2022 at 15:37, Ilya Leoshkevich <iii@linux.ibm.com>
> wrote:
> > 
> > On Tue, 2022-07-05 at 14:57 +0100, Peter Maydell wrote:
> > > On Tue, 5 Jul 2022 at 14:04, Daniel P. Berrangé
> > > <berrange@redhat.com>
> > > wrote:
> > > > If we put this job in QEMU CI someone will have to be able to
> > > > interpret the results when it fails.
> > > 
> > > In particular since this is qemu-user, the answer is probably
> > > at least some of the time going to be "oh, well, qemu-user isn't
> > > reliable
> > > if you do complicated things in the guest". I'd be pretty wary of
> > > our
> > > having
> > > a "pass a big complicated guest code test suite under linux-user
> > > mode"
> > > in the CI path.
> 
> > Actually exercising qemu-user is one of the goals here: just as an
> > example, one of the things that the test suite found was commit
> > 9a12adc704f9 ("linux-user/s390x: Fix unwinding from signal
> > handlers"),
> > so it's not only about the ISA.
> > 
> > At least for s390x, we've noticed that various projects use
> > qemu-user-based setups in their CI (either calling it explicitly,
> > or
> > via binfmt-misc), and we would like these workflows to be reliable,
> > even if they try complicated (within reason) things there.
> 
> I also would like them to be reliable. But I don't think
> *testing* these things is the difficulty: it is having
> people who are willing to spend time on the often quite
> difficult tasks of identifying why something intermittently
> fails and doing the necessary design and implementation work
> to correct the problem. Sometimes this is easy (as in the
> s390 regression above) but quite often it is not (eg when
> multiple threads are in use, or the guest wants to do
> something complicated with clone(), etc).
> 
> thanks
> -- PMM
> 

For what it's worth, we can help analyzing and fixing failures detected
by the s390x wasmtime job. If something breaks, we will have to look at
it anyway, and it's better to do this sooner than later.

Best regards,
Ilya


  reply	other threads:[~2022-07-05 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 22:48 [RFC] gitlab: introduce s390x wasmtime job Ilya Leoshkevich
2022-07-05 12:58 ` Daniel P. Berrangé
2022-07-05 13:57   ` Peter Maydell
2022-07-05 14:37     ` Ilya Leoshkevich
2022-07-05 14:40       ` Peter Maydell
2022-07-05 20:41         ` Ilya Leoshkevich [this message]
2022-12-16 15:10           ` Alex Bennée
2022-12-19 21:42             ` Ilya Leoshkevich
2022-12-19 22:18               ` Alex Bennée
2022-07-05 14:13   ` Ilya Leoshkevich

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=ad7a0620ca3279ab857050b2850f3e1e330539c7.camel@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=bleal@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=ulrich.weigand@de.ibm.com \
    --cc=wainersm@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).