Re: [Xen-devel] [linux-3.18 test] 62651: regressions - FAIL

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [linux-3.18 test] 62651: regressions - FAIL"):
> On Tue, 2015-10-06 at 04:21 +0000, osstest service owner wrote:
> 2015-10-06 00:50:13 Z guest redhat.guest.osstest 5a:36:0e:bb:00:3a 22 
> link/ip/tcp: ok. (35s)
> 2015-10-06 00:50:13 Z executing ssh ... root@xxxxxxxxxxxxxx echo guest 
> redhat.guest.osstest: ok
> 2015-10-06 00:50:43 Z command timed out [30]: timeout 60 ssh -o 
> StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o 
> ServerAliveInterval=100 -o PasswordAuthentication=no -o 
> ChallengeResponseAuthentication=no -o 
> UserKnownHostsFile=tmp/t.known_hosts_62651.test-amd64-i386-qemut-rhel6hvm-amd 
> root@xxxxxxxxxxxxxx echo guest redhat.guest.osstest: ok
> status (timed out) at Osstest/TestSupport.pm line 410.

This is quite different: it's a timeout.  And, a 30s one.

> I think it is specific to merlot and will work itself out next time. From
> http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-qemut-rhel6hvm-amd/linux-3.18.html
> there was one similar failure months ago which succeeded on a second attempt.

I just looked at a Debian HVM stubom failure in the osstest baseline
62620:

http://logs.test-lab.xenproject.org/osstest/logs/62620/test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm/info.html

That was a 10s timeout but otherwise very similar.  There wasn't
enough information in the logs to see anything wrong.

We don't seem to have a useable guest console log in these tests.

Ian.

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