From: Wei Liu <wei.liu2@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jim Fehlig <jfehlig@suse.com>,
xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Policy for force pushing smoke branch Was: Re: [xen-unstable-smoke test] 88656: regressions - FAIL
Date: Mon, 4 Apr 2016 14:28:48 +0100 [thread overview]
Message-ID: <20160404132848.GA3116@citrix.com> (raw)
In-Reply-To: <osstest-88656-mainreport@xen.org>
On Mon, Apr 04, 2016 at 01:15:53PM +0000, osstest service owner wrote:
> flight 88656 xen-unstable-smoke real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/88656/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
>
> Tests which did not succeed, but are not blocking:
> test-amd64-amd64-libvirt 1 build-check(1) blocked n/a
This failed because libvirt doesn't set LIBXL_API_VERSION. It is not a
bug in Xen code base.
I don't think we have precedent of force-pushing smoke branch, so we
need to decide what to do here.
It would take some time for libvirt fix to land and propagate to our own
mirror. I would like to avoid holding backing xen.git push for too long
if possible. So I'm for force-pushing the smoke branch and subsequently
master branch if necessary.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-04 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 18:53 [xen-unstable test] 88588: regressions - FAIL osstest service owner
2016-04-04 15:58 ` [xen-unstable-smoke test] 88672: " osstest service owner
2016-04-04 13:15 ` [xen-unstable-smoke test] 88656: " osstest service owner
2016-04-04 13:28 ` Wei Liu [this message]
2016-04-04 13:32 ` Policy for force pushing smoke branch Was: " Ian Jackson
2016-04-04 16:55 ` Policy for force pushing smoke branch Was: Re: [xen-unstable-smoke test] 88656: regressions - FAIL [and 1 more messages] Ian Jackson
2016-04-05 10:31 ` Policy for force pushing smoke branch Was: Re: [xen-unstable-smoke test] 88656: regressions - FAIL [and 1 more messages] " Ian Jackson
2016-04-05 10:36 ` Wei Liu
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=20160404132848.GA3116@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jfehlig@suse.com \
--cc=osstest-admin@xenproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).