From: Nadav Amit <namit@vmware.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
Wanpeng Li <kernellwp@gmail.com>,
David Hildenbrand <david@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Thomas Huth <thuth@redhat.com>, KVM <kvm@vger.kernel.org>,
Laurent Vivier <lvivier@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Liran Alon <liran.alon@oracle.com>,
Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: A new name for kvm-unit-tests ?
Date: Thu, 30 Jul 2020 17:36:42 +0000 [thread overview]
Message-ID: <EA3D04A5-3144-4F0B-B7D5-A99DB0FC4818@vmware.com> (raw)
In-Reply-To: <2b07717e-3716-cc55-8f1b-8047a318c1f2@redhat.com>
> On Jul 30, 2020, at 10:35 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 30/07/20 19:32, Nadav Amit wrote:
>>> We can use compile-time or run-time logic that depends on the target to
>>> decide whether a test should be a normal test (pass/fail) or an
>>> xpass/xfail test.
>> This is simple. When I find some time, I will send some patches for that.
>
> Not too quick, let's first look at a design.
Don’t worry, I am busy ;-)
The subtext of my response was that a fully fledged errata mechanism is more
complicated.
next prev parent reply other threads:[~2020-07-30 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 5:41 A new name for kvm-unit-tests ? Thomas Huth
2020-07-30 6:38 ` Christian Borntraeger
2020-07-30 7:09 ` David Hildenbrand
2020-07-30 7:13 ` Wanpeng Li
2020-07-30 7:35 ` Paolo Bonzini
2020-07-30 7:50 ` Nadav Amit
2020-07-30 11:32 ` Andrew Jones
2020-07-30 13:33 ` Paolo Bonzini
2020-07-30 17:32 ` Nadav Amit
2020-07-30 17:35 ` Paolo Bonzini
2020-07-30 17:36 ` Nadav Amit [this message]
2020-07-31 5:53 ` Thomas Huth
2020-07-31 6:18 ` Andrew Jones
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=EA3D04A5-3144-4F0B-B7D5-A99DB0FC4818@vmware.com \
--to=namit@vmware.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=thuth@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).