From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Subject: Re: [linux-3.4 test] 62189: trouble: pass/preparing/queued
Date: Tue, 22 Sep 2015 11:37:53 +0100 [thread overview]
Message-ID: <1442918273.10338.136.camel@citrix.com> (raw)
In-Reply-To: <osstest-62189-mainreport@xen.org>
On Tue, 2015-09-22 at 10:34 +0000, osstest service owner wrote:
> flight 62189 linux-3.4 running [real]
> http://logs.test-lab.xenproject.org/osstest/logs/62189/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-i386-pvgrub <none executed> queued
This was running with a version of the test harness which didn't yet
understand about the minimum kernel requirements for some machines and
hence wasn't going to be any more successful than the last 219 attempts...
The next flight will pick up that new code and should therefore have some s
ort of chance of passing...
Ian.
prev parent reply other threads:[~2015-09-22 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 10:34 [linux-3.4 test] 62189: trouble: pass/preparing/queued osstest service owner
2015-09-22 10:37 ` 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=1442918273.10338.136.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 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).