From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Ian Campbell <ian.campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Robert Hu <robert.hu@intel.com>, KevinTian <kevin.tian@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
osstestservice owner <osstest-admin@xenproject.org>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [xen-unstable test] 65141: regressions - FAIL
Date: Wed, 2 Dec 2015 10:57:35 +0000 [thread overview]
Message-ID: <565ECE9F.6030609@citrix.com> (raw)
In-Reply-To: <565EDB7802000078000BB2E0@prv-mh.provo.novell.com>
On 02/12/15 10:52, Jan Beulich wrote:
>>>> On 02.12.15 at 11:34, <ian.campbell@citrix.com> wrote:
>> On Mon, 2015-11-30 at 05:35 +0000, Hu, Robert wrote:
>>
>> Also adding Vt-x maintainers (Kevin and Jun) for their help/input, I'm not
>> sure if there is a dedicated nested-vmx maintainer. This failure has been
>> blocking the xen-unstable push gate for a week now so it really does need
>> looking into.
>>
>> Also CC the arch X86 maintainers, for-their-info.
> I was actually waiting for the bisector to point at something. Also
> looking at the history this might be machine specific (the sole
> initial pass was on italia0, all failures are on godello1). Should new
> tests perhaps be capable of causing regressions only once they
> passed on every host they may (usefully) run on?
As a general improvement, OSSTest should not make new tests blocking by
default. They should need to be proved stable (5 consecutive passes?)
before they become blocking, to prevent a new test spuriously passing
and subsequently blocking pushes.
During this time, the author of the new test has the onus to ensure test
stability; either modifications to the test, or bugfixes to master.
~Andrew
next prev parent reply other threads:[~2015-12-02 10:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 15:45 [xen-unstable test] 65141: regressions - FAIL osstest service owner
2015-11-27 15:54 ` Ian Jackson
2015-11-30 5:35 ` Hu, Robert
2015-12-02 10:34 ` Ian Campbell
2015-12-02 10:52 ` Jan Beulich
2015-12-02 10:57 ` Andrew Cooper [this message]
2015-12-02 11:07 ` Ian Campbell
2015-12-02 13:51 ` Ian Campbell
2015-12-03 5:58 ` Tian, Kevin
2015-12-03 9:25 ` Ian Campbell
2015-12-05 8:09 ` Ian Campbell
2015-12-07 16:18 ` Jan Beulich
2015-12-07 16:28 ` Ian Campbell
2015-12-07 16:48 ` Jan Beulich
2015-12-08 2:46 ` Tian, Kevin
2015-12-08 7:28 ` Jan Beulich
2015-12-08 8:06 ` Hu, Robert
2015-12-08 10:29 ` Ian Campbell
2015-12-09 6:27 ` Robert Hu
2015-12-09 8:35 ` Jin, Gordon
2015-12-09 10:21 ` Ian Campbell
2015-12-11 4:04 ` Robert Hu
2015-12-11 11:49 ` Ian Campbell
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=565ECE9F.6030609@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=osstest-admin@xenproject.org \
--cc=robert.hu@intel.com \
--cc=xen-devel@lists.xensource.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.