All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, "xen.org" <Ian.Jackson@eu.citrix.com>
Subject: Re: [libvirt test] 33157: regressions - trouble:	blocked/fail/pass/preparing/queued
Date: Thu, 08 Jan 2015 10:16:38 -0700	[thread overview]
Message-ID: <54AEBB76.2060801@suse.com> (raw)
In-Reply-To: <1420735534.19787.114.camel@citrix.com>

Ian Campbell wrote:
> On Thu, 2015-01-08 at 09:37 -0700, Jim Fehlig wrote:
>   
>> xen.org wrote:
>>     
>>> flight 33157 libvirt running [real]
>>> http://www.chiark.greenend.org.uk/~xensrcts/logs/33157/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>>  build-amd64-libvirt             <none executed>              queued
>>>  test-amd64-i386-libvirt         <none executed>              queued
>>>  test-amd64-amd64-libvirt        <none executed>              queued
>>>  build-armhf-libvirt           5 libvirt-build             fail REGR. vs. 32648
>>>  build-i386-libvirt            5 libvirt-build             fail REGR. vs. 32648
>>>   
>>>       
>> The build failure here was
>>
>> make[2]: *** No rule to make target `xenconfig/xen_xl_disk.h', needed by
>> `all'. Stop.
>>
>> Now fixed with libvirt commits edacdb3d and 533349ff.
>>     
>
> Great, thanks for the heads up.
>
> It looks like libvirt has imported the disk syntax parser stuff from
> xen.git/tools/libxl/libxlu_disk_l.l?

Yes.

> Why not just use libxlu.so which
> Xen ships containing that code? We do so pretty much exactly because we
> thought it would be useful to libvirt...
>   

Because I didn't know :-(.  And yes, it would be useful to libvirt, and
would have saved myself and others considerable time.  In hindsight, I
should have cc'd xen-devel on the original patch series.  I think Wei
was the only Xen tools dev to review the series, and he too missed your
suggestion.

> I must confess that I thought you already did use libxlu...
>   

No, not directly.  But I will be doing so now.  I should try to revert
all this nonsense and use libxlu before it ends up in the next libvirt
release.

Thanks a lot Ian!

Regards,
Jim

  reply	other threads:[~2015-01-08 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 14:02 [libvirt test] 33157: regressions - trouble: blocked/fail/pass/preparing/queued xen.org
2015-01-08 16:37 ` Jim Fehlig
2015-01-08 16:45   ` Ian Campbell
2015-01-08 17:16     ` Jim Fehlig [this message]
2015-01-08 21:56       ` Jim Fehlig
2015-01-09  5:59         ` Jim Fehlig
2015-01-09  9:27         ` Ian Campbell
2015-01-09 16:59         ` Dario Faggioli
2015-01-09 17:55           ` Jim Fehlig
2015-01-19 17:00         ` Ian Campbell
2015-01-19 17:42           ` Ian Jackson

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=54AEBB76.2060801@suse.com \
    --to=jfehlig@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.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.