xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "xen.org" <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, John.Dilley@citrix.com
Subject: Re: [xen-unstable test] 21977: trouble: blocked/broken/fail/pass
Date: Sun, 17 Nov 2013 09:24:51 +0000	[thread overview]
Message-ID: <1384680291.19913.1.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <osstest-21977-mainreport@xen.org>

On Sun, 2013-11-17 at 02:45 +0000, xen.org wrote:
> flight 21977 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/21977/
> 
> Failures and problems with tests :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-armhf                   2 host-install(2)         broken REGR. vs. 21938

Seems that xenuse requires a new python module:
        2013-11-16 17:16:56 Z power: setting 0 for marilith-n5
        2013-11-16 17:16:56 Z XenUse overriding $USER to osstest
        Traceback (most recent call last):
          File "/usr/groups/xenrt/production/share/control/xenrt", line 8, in <module>
            import sys, string, getopt, urllib, os, pwd, tempfile, xmlrpclib, shutil, json
        ImportError: No module named json
        Traceback (most recent call last):
          File "/usr/groups/xenrt/production/share/control/xenrt", line 8, in <module>
            import sys, string, getopt, urllib, os, pwd, tempfile, xmlrpclib, shutil, json
        ImportError: No module named json

I have installed python-json on woking and xenuse seems happy now.

Ian.

  reply	other threads:[~2013-11-17  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17  2:45 [xen-unstable test] 21977: trouble: blocked/broken/fail/pass xen.org
2013-11-17  9:24 ` Ian Campbell [this message]
2013-11-18 11:05   ` Ian Jackson
2013-11-19  9:37     ` Ian Campbell
2013-11-20 14:36       ` Ian Jackson

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=1384680291.19913.1.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=John.Dilley@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --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).