From: Chris J Arges <chris.j.arges@canonical.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-unit-test failures
Date: Fri, 29 Aug 2014 16:18:38 -0500 [thread overview]
Message-ID: <5400EE2E.1000408@canonical.com> (raw)
In-Reply-To: <5400EBD9.6070204@redhat.com>
On 08/29/2014 04:08 PM, Paolo Bonzini wrote:
> Il 29/08/2014 19:36, Chris J Arges ha scritto:
>> I still get failures with the following test, I actually tested on
>> multiple machines with identical hardware and the same failure occurred.
>> In v3.13/v3.16 series kernels this passes. I'll look into which commit
>> changed this result for me. I suspect it was fairly recent.
>
> I would try bisecting between 0e5ac3a8b100469ea154f87dd57b685fbdd356f6
> (might be bad) and 41fa4215f8e8150bdc5d2a5f8704915f1b059fa8 (might be good).
>
Just sent the other email with my bisect results, the 'bad' commit for
me is:
0d3da0d26e3c3515997c99451ce3b0ad1a69a36c
A revert on this commit allows the tests to pass again.
> Is this a laptop or desktop? Any relationship between the "Offset" and
> how long the machine has been up?
>
> Paolo
>
This is a server; and no, I've reboot the machine and re-run the test.
I've also run it after days of uptime.
--chris
next prev parent reply other threads:[~2014-08-29 21:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 18:29 [PATCH 0/2] kvm-unit-tests: add check parameter to run_tests configuration Chris J Arges
2014-08-26 18:29 ` [PATCH 1/2] " Chris J Arges
2014-08-27 13:29 ` Paolo Bonzini
2014-08-27 14:42 ` [PATCH 1/2 v2] " Chris J Arges
2014-08-27 14:45 ` [PATCH 1/2 v3] " Chris J Arges
2014-08-27 14:52 ` Paolo Bonzini
2014-08-27 21:24 ` kvm-unit-test failures (was: [PATCH 1/2 v3] add check parameter to run_tests configuration) Chris J Arges
2014-08-27 22:05 ` Paolo Bonzini
2014-08-29 17:36 ` kvm-unit-test failures Chris J Arges
2014-08-29 21:05 ` Chris J Arges
2014-08-31 16:05 ` Paolo Bonzini
2014-09-02 19:57 ` Chris J Arges
2014-09-03 14:47 ` Paolo Bonzini
2014-09-03 15:21 ` Chris J Arges
2014-09-03 14:59 ` Paolo Bonzini
2014-09-03 16:23 ` Chris J Arges
2014-09-03 17:52 ` Paolo Bonzini
2014-09-03 18:25 ` Chris J Arges
[not found] ` <54083688.6000201@redhat.com>
2014-09-04 11:33 ` Paolo Bonzini
2014-09-04 12:24 ` Wanpeng Li
2014-09-04 13:11 ` Paolo Bonzini
2014-08-29 21:08 ` Paolo Bonzini
2014-08-29 21:18 ` Chris J Arges [this message]
2014-08-26 18:29 ` [PATCH 2/2] x86/unittests.cfg: the pmu testcase requires that nmi_watchdog is disabled Chris J Arges
2014-08-27 13:29 ` Paolo Bonzini
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=5400EE2E.1000408@canonical.com \
--to=chris.j.arges@canonical.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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 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.