xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Jim Fehlig <jfehlig@suse.com>,
	xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: Policy for force pushing smoke branch Was: Re: [xen-unstable-smoke test] 88656: regressions - FAIL [and 1 more messages] [and 1 more messages]
Date: Tue, 5 Apr 2016 11:36:01 +0100	[thread overview]
Message-ID: <20160405103601.GA17563@citrix.com> (raw)
In-Reply-To: <22275.37889.734817.85569@mariner.uk.xensource.com>

On Tue, Apr 05, 2016 at 11:31:29AM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Policy for force pushing smoke branch Was: Re: [Xen-devel] [xen-unstable-smoke test] 88656: regressions - FAIL [and 1 more messages]"):
> > I'll do a force push to xen.git#master if this is the only blocker,
> > too.  Also, any necessary force push of the osstest tested libvirt
> > branch.
> 
> Looking at the state of the main xen-unstable tests, I'm not so sure
> this is the right approach:
> 
> osstest service owner writes ("[xen-unstable test] 88588: regressions - FAIL"):
> > flight 88588 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/88588/
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs. 86491
> >  test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs. 86491
> 
> We are still investigating this.  But this failure will be masked if
> the libvirt build fails.
> 
> Do we expect a fix to the libvirt API issue soon ?
> 

I'm waiting for Jim's reply on the correct approach to fix libvirt. Once
he replies I will submit a patch to libvirt. I don't anticipate the
patch to be complicated.

Wei.

> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-04-05 10:36 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     ` Policy for force pushing smoke branch Was: " Wei Liu
2016-04-04 13:32       ` 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 [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=20160405103601.GA17563@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).