From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, osstest-admin@xenproject.org
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 65094: regressions - FAIL
Date: Thu, 26 Nov 2015 09:24:00 +0000 [thread overview]
Message-ID: <1448529840.17688.145.camel@citrix.com> (raw)
In-Reply-To: <5656D71C02000078000B943D@prv-mh.provo.novell.com>
On Thu, 2015-11-26 at 01:55 -0700, Jan Beulich wrote:
> > > > On 25.11.15 at 20:32, <osstest-admin@xenproject.org> wrote:
> > flight 65094 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/65094/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR.
> > vs. 64035
>
> This being the only regression and ...
>
> > version targeted for testing:
> > xen 0c3f24645b07b875bc1294fb4627f01e030690fe
> > baseline version:
> > xen 22a1fbb575df3a3a7726cdeb5ddf19cc8f60827c
>
> ... this not being the commit force pushed yesterday, I think this
> warrants another force push.
22a1fbb575df3a3a7726cdeb5ddf19cc8f60827c is before
827db7b26384ce083df7154d77f13379b2cf4121, and 22a1fbb was also the basis
for flight 65066 which was the other force push.
So all that has happened is that this flight was already under way when I
did the force push. The currently in progress flight (65114) will use the
new baseline and therefore not thing test-amd64-i386-rumpuserxen-i386 is
regressing any longer.
So while we could force push we can also just wait for 65114.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-11-26 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 19:32 [xen-unstable test] 65094: regressions - FAIL osstest service owner
2015-11-26 8:55 ` Jan Beulich
2015-11-26 9:24 ` Ian Campbell [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=1448529840.17688.145.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=osstest-admin@xenproject.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.