From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris J Arges <chris.j.arges@canonical.com>, kvm@vger.kernel.org
Subject: Re: kvm-unit-tests failures
Date: Sat, 02 Aug 2014 08:35:27 +0200 [thread overview]
Message-ID: <53DC86AF.7080604@redhat.com> (raw)
In-Reply-To: <53DC01F8.2080800@canonical.com>
Il 01/08/2014 23:09, Chris J Arges ha scritto:
> Hi,
>
> We are planning on running kvm-unit-tests as part of our test suite; but
> I've noticed that many tests fail (even running the latest kvm tip).
> After searching I found many BZ entires that seem to point at this
> master bug for tracking these issues:
> https://bugzilla.redhat.com/show_bug.cgi?id=1079979
This bug is for failures in the RHEL7 kernel, which is older than
kvm.git. Which tests fail for you?.
kvm.git bugs are tracked in bugzilla.kernel.org, but for now I think
it's better if you just reply here.
Paolo
> However, this bug is private; and cannot be viewed by the public.
>
> I'd like to know how to help report issues that we observe with testing
> in order to help fix these tests, or understand any progress being made
> to fix them already. Is there a public bug that everybody can view to
> track these issues? Should I be reporting new bugs with failures in the
> unit tests? Where is the appropriate place to file bugs against
> kvm-unit-tests and discuss issues?
>
> Thanks,
> --chris j arges
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-08-02 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 21:09 kvm-unit-tests failures Chris J Arges
2014-08-02 6:35 ` Paolo Bonzini [this message]
2014-08-04 17:02 ` Chris J Arges
2014-08-04 18:20 ` Paolo Bonzini
2014-08-04 18:37 ` Chris J Arges
2014-08-04 18:40 ` Paolo Bonzini
2014-08-04 18:44 ` Chris J Arges
2014-08-05 10:26 ` Paolo Bonzini
2014-08-05 14:46 ` Eduardo Habkost
2014-08-05 18:26 ` Chris J Arges
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=53DC86AF.7080604@redhat.com \
--to=pbonzini@redhat.com \
--cc=chris.j.arges@canonical.com \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.