Re: [Xen-devel] [xen-unstable test] 20890: trouble: blocked/broken/fail/pass

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2013-10-15 at 08:28 +0100, Ian Campbell wrote:
> On Tue, 2013-10-15 at 06:26 +0100, xen.org wrote:
> > flight 20890 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/20890/
> > 
> > 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. 
> > 20855
> >  build-armhf-pvops             2 host-install(2)         broken REGR. vs. 
> > 20855
> 
> From
> http://www.chiark.greenend.org.uk/~xensrcts/logs/20890/build-armhf/2.ts-host-install-twice.log
> 
>         2013-10-14 22:38:02 Z power: setting 0 for marilith-n5
>         Traceback (most recent call last):
>           File "/usr/groups/xencore/systems/bin/xenuse", line 388, in <module>
>             main()
>           File "/usr/groups/xencore/systems/bin/xenuse", line 356, in main
>             machine.power(optPower, optForce)
>           File "/usr/groups/xencore/systems/bin/xenuse", line 113, in power
>             self.checkLocked(optForce, allowUnlocked = True)
>           File "/usr/groups/xencore/systems/bin/xenuse", line 83, in 
> checkLocked
>             if l.strip() == ("LEASEUSER='%s'" % os.environ["USER"]):
>           File "/usr/lib/python2.5/UserDict.py", line 22, in __getitem__
>             raise KeyError(key)
>         KeyError: 'USER'
>         /usr/groups/xencore/systems/bin/xenuse --off marilith-n5: 256  at 
> Osstest.pm line 275.
>         
> Looks like someone was messing with xenuse. Running it by hand this
> morning it seems to be OK now...
> 
> Unless perhaps osstest is stripping $USER from the environment? If it is
> then grep doesn't see where...

It turns out $USER is not required by any spec and cron (which runs
osstest) does not set it. xenuse has been fixed to not rely on $USER.

> 
> I'm also now wondering how this ever worked, since the machines are
> xenuse locked by me and the tests are run as osstest, so xenuse ought to
> be rejecting attempts by osstest to do power control...
> 
> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel