From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>
Subject: Re: [xen-unstable test] 59681: regressions - FAIL
Date: Mon, 20 Jul 2015 09:28:45 +0100 [thread overview]
Message-ID: <55ACB13D.7070301@citrix.com> (raw)
In-Reply-To: <20150720082454.GA1938@zion.uk.xensource.com>
On 20/07/2015 09:24, Wei Liu wrote:
> On Mon, Jul 20, 2015 at 09:18:48AM +0100, Andrew Cooper wrote:
>> On 18/07/2015 13:07, osstest service owner wrote:
>>> flight 59681 xen-unstable real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/59681/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>> test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail REGR. vs. 58965
>>> test-amd64-i386-xl-qemuu-debianhvm-amd64 9 debian-hvm-install fail REGR. vs. 58965
>> Wei: Am I correct in remembering that you nominated these two tests for
>> being added to the allowable category?
>>
> Only the first one should be marked allowable.
>
> The second failure looks spurious. In the next xen-unstable run, it
> passed.
Ah yes - so it did. Should we do a force push then? It appears that
subsequent runs started hitting problems when cloning repos to build.
~Andrew
prev parent reply other threads:[~2015-07-20 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 12:07 [xen-unstable test] 59681: regressions - FAIL osstest service owner
2015-07-20 8:18 ` Andrew Cooper
2015-07-20 8:24 ` Wei Liu
2015-07-20 8:28 ` Andrew Cooper [this message]
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=55ACB13D.7070301@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=wei.liu2@citrix.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.