From: Jim Fehlig <jfehlig@suse.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: [libvirt test] 151910: regressions - FAIL
Date: Thu, 23 Jul 2020 15:42:57 -0600 [thread overview]
Message-ID: <8aa2f4c4-752c-8339-f34c-18025e3377dc@suse.com> (raw)
In-Reply-To: <5b44b5dc-bc37-bdaa-47a4-5f5b72392f45@suse.com>
On 7/15/20 1:53 PM, Jim Fehlig wrote:
> On 7/15/20 9:07 AM, osstest service owner wrote:
>> flight 151910 libvirt real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/151910/
>>
>> 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. 151777
>> build-i386-libvirt 6 libvirt-build fail REGR. vs. 151777
>> build-arm64-libvirt 6 libvirt-build fail REGR. vs. 151777
>> build-armhf-libvirt 6 libvirt-build fail REGR. vs. 151777
>
> I see the same configure failure has been encountered since July 11
>
> checking for XDR... no
> configure: error: You must install the libtirpc >= 0.1.10 pkg-config module to
> compile libvirt
>
> AFAICT there have been no related changes in libvirt (which has required
> libtirpc for over two years).
Sorry for the mistake. There has been a change in libvirt
https://gitlab.com/libvirt/libvirt/-/commit/d7147b3797380de2d159ce6324536f3e1f2d97e3
My reputation for OSSTEST patches is not the greatest, but I took a stab at it
regardless :-)
https://lists.xenproject.org/archives/html/xen-devel/2020-07/msg01208.html
Regards,
Jim
prev parent reply other threads:[~2020-07-23 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 15:07 [libvirt test] 151910: regressions - FAIL osstest service owner
2020-07-15 19:53 ` Jim Fehlig
2020-07-23 21:42 ` 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=8aa2f4c4-752c-8339-f34c-18025e3377dc@suse.com \
--to=jfehlig@suse.com \
--cc=ian.jackson@eu.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.