Re: [Xen-devel] [xen-unstable test] 13302: regressions - FAIL

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [Xen-devel] [xen-unstable test] 13302: regressions - 
FAIL"):
> On Fri, 2012-06-22 at 04:00 +0100, xen.org wrote:
> > flight 13302 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/13302/
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  build-i386-pvops              4 kernel-build        fail REGR. vs. 13025
...
> These all appear to be timeouts -- some sort of infrastructure problem?

I think so.  It seems that the build host became unresponsive via the
network.  But the serial console log shows it apparently happy.
Well, no messages, anyway.  Perhaps it crashed.  That host has been
wiped since.

...
> >  test-amd64-amd64-xl-win       7 windows-install       fail REGR. vs. 13025
...
> 
> These are also timeouts but of the guest initial boot/install. Could be
> related to the infrastructure issues?

I don't think so.  There is no sign of anything along those lines and
the dom0 and tester keep talking to each other just fine.  If the
switch was broken or something, it wouldn't have had a dhcp server but
I would have expected the domain to still exist.

What seems to have happened here is that the guest tried to reboot but
xl didn't start the new instance.  The xl log says:

  Waiting for domain win.guest.osstest (domid 1) to die [pid 2679]
  Domain 1 has shut down, reason code 1 0x1
  Action for shutdown reason code 1 is restart
  Domain 1 needs to be cleaned up: destroying the domain

And the dom0 kernel log says:

 Jun 21 23:59:45 moss-bug kernel: [  789.115260] xl[2679]: segfault at
 7f346c000000 ip 00007f346e817919 sp 00007fffb95adcf0 error 4 in
 libc-2.11.3.so[7f346e7a1000+159000]

Ian.

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