From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
osstest-admin@xenproject.org, Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-4.5-testing test] 102601: regressions - FAIL
Date: Fri, 25 Nov 2016 08:52:14 +0000 [thread overview]
Message-ID: <20161125085214.GO23528@citrix.com> (raw)
In-Reply-To: <5838067202000078001221B1@prv-mh.provo.novell.com>
On Fri, Nov 25, 2016 at 01:37:54AM -0700, Jan Beulich wrote:
> >>> On 25.11.16 at 04:14, <osstest-admin@xenproject.org> wrote:
> > flight 102601 xen-4.5-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/102601/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-armhf-armhf-libvirt 13 saverestore-support-check fail REGR. vs. 101275
>
> Since this is recurring, does anyone have an idea what may have
> changed? Looking at the "Last pass / First worst fail" row of the
> results table I see quite a few other ARM tests which appear to
> be known to fail this step, so I wonder whether there has been an
> earlier unexpected pass of this step for whatever reason.
>
We need to force push this tree.
At one point Ian changed that job to always fail, hence osstest thinks
it is a regression.
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-11-25 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 3:14 [xen-4.5-testing test] 102601: regressions - FAIL osstest service owner
2016-11-25 8:37 ` Jan Beulich
2016-11-25 8:52 ` Wei Liu [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=20161125085214.GO23528@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=osstest-admin@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.