From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>
Cc: xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com
Subject: Re: [ovmf test] 59044: trouble: blocked/broken/fail/pass
Date: Mon, 6 Jul 2015 09:34:45 +0100 [thread overview]
Message-ID: <1436171685.25646.8.camel@citrix.com> (raw)
In-Reply-To: <osstest-59044-mainreport@xen.org>
On Fri, 2015-07-03 at 22:40 +0000, osstest service owner wrote:
> flight 59044 ovmf real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/59044/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i386 4 capture-logs !broken [st=!broken!]
Seems to be Osstest/JobDB/Executive.pm line 137:
die Dumper($ho)." ?" if $ho->{SharedOthers} && !
$ho->{SharedReady};
So another sharing related glitch, like the linux-3.18 flight 59041 I
just pointedy ou at (which was on armhf though).
Any ideas?
next prev parent reply other threads:[~2015-07-06 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 22:40 [ovmf test] 59044: trouble: blocked/broken/fail/pass osstest service owner
2015-07-06 8:34 ` Ian Campbell [this message]
2015-07-06 10:30 ` Ian Jackson
2015-07-06 10:35 ` Ian Campbell
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=1436171685.25646.8.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.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).