From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Subject: Re: [qemu-mainline test] 62725: trouble: broken/fail/pass
Date: Fri, 9 Oct 2015 11:38:34 +0100 [thread overview]
Message-ID: <1444387114.1410.329.camel@citrix.com> (raw)
In-Reply-To: <osstest-62725-mainreport@xen.org>
On Fri, 2015-10-09 at 10:33 +0000, osstest service owner wrote:
> flight 62725 qemu-mainline real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/62725/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-multivcpu 3 host-install(3) broken REGR. vs. 62649
> test-amd64-amd64-xl-xsm 3 host-install(3) broken REGR. vs. 62649
> test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken REGR. vs. 62649
> test-amd64-amd64-amd64-pvgrub 3 host-install(3) broken REGR. vs. 62649
> test-amd64-i386-freebsd10-i386 3 host-install(3) broken REGR. vs. 62649
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 3 host-install(3) broken REGR. vs. 62649
These all look like elbling0 forgetting its boot order.
>
> Regressions which are regarded as allowable (not blocking):
> test-amd64-i386-libvirt 3 host-install(3) broken REGR. vs. 62649
> test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken REGR. vs. 62649
> test-amd64-i386-libvirt-qcow2 3 host-install(3) broken REGR. vs. 62649
> test-amd64-i386-libvirt-vhd 3 host-install(3) broken REGR. vs. 62649
So do these.
prev parent reply other threads:[~2015-10-09 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 10:33 [qemu-mainline test] 62725: trouble: broken/fail/pass osstest service owner
2015-10-09 10:38 ` Ian Campbell [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=1444387114.1410.329.camel@citrix.com \
--to=ian.campbell@citrix.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 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.