All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [libvirt test] 149773: regressions - FAIL
Date: Thu, 4 Jun 2020 09:57:21 -0600	[thread overview]
Message-ID: <f803ba59-4f9d-f300-8335-9c8f0ce22757@suse.com> (raw)
In-Reply-To: <24280.60980.488961.267238@mariner.uk.xensource.com>

On 6/4/20 6:51 AM, Ian Jackson wrote:
> Jim Fehlig writes ("Re: [libvirt test] 149773: regressions - FAIL"):
>> On 4/24/20 3:53 AM, osstest service owner wrote:
>>> flight 149773 libvirt real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/149773/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>>    build-amd64-libvirt           6 libvirt-build            fail REGR. vs. 146182
>>>    build-i386-libvirt            6 libvirt-build            fail REGR. vs. 146182
>>>    build-arm64-libvirt           6 libvirt-build            fail REGR. vs. 146182
>>>    build-armhf-libvirt           6 libvirt-build            fail REGR. vs. 146182
>>
>> Probably best to disable these tests to avoid all the spam.
> 
> I have fixed the build bug now...

I saw your patch on the libvirt dev list, thanks! I'm a bit embarrassed for not 
considering a fix on the libvirt side while trying to address this a few months 
back :-/.

I suspect the upcoming move to meson will be a bit more disruptive and will 
likely require changes to osstest.

Regards,
Jim


      reply	other threads:[~2020-06-04 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  9:53 [libvirt test] 149773: regressions - FAIL osstest service owner
2020-04-24 20:37 ` Jim Fehlig
2020-06-04 12:51   ` Ian Jackson
2020-06-04 15:57     ` Jim Fehlig [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=f803ba59-4f9d-f300-8335-9c8f0ce22757@suse.com \
    --to=jfehlig@suse.com \
    --cc=ian.jackson@citrix.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.