From: Jim Fehlig <jfehlig@suse.com>
To: osstest service owner <osstest-admin@xenproject.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [libvirt test] 79891: regressions - FAIL
Date: Tue, 02 Feb 2016 14:48:06 -0700 [thread overview]
Message-ID: <56B12416.8090507@suse.com> (raw)
In-Reply-To: <osstest-79891-mainreport@xen.org>
osstest service owner wrote:
> flight 79891 libvirt real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/79891/
>
> 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. 79451
> build-i386-libvirt 5 libvirt-build fail REGR. vs. 79451
> build-armhf-libvirt 5 libvirt-build fail REGR. vs. 79451
FYI, this should already be fixed by
http://libvirt.org/git/?p=libvirt.git;a=commit;h=0d0e41a71910e0415a924648f44a0b00389a576a
Regards,
Jim
prev parent reply other threads:[~2016-02-02 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 15:28 [libvirt test] 79891: regressions - FAIL osstest service owner
2016-02-02 21:48 ` 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=56B12416.8090507@suse.com \
--to=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).