From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [linux-3.18 test] 62651: regressions - FAIL Date: Tue, 6 Oct 2015 11:55:31 +0100 Message-ID: <1444128931.5302.128.camel@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: osstest service owner , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, 2015-10-06 at 04:21 +0000, osstest service owner wrote: > flight 62651 linux-3.18 real [real] > http://logs.test-lab.xenproject.org/osstest/logs/62651/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-i386-qemut-rhel6hvm-amd 12 guest-start/redhat.repeat fail REGR. vs. 58581 http://logs.test-lab.xenproject.org/osstest/logs/62651/test-amd64-i386-qemut-rhel6hvm-amd/12.ts-repeat-test.log Contains something awfully similar seeming to the sshd restart thing which was just fixed on Debian: 2015-10-06 00:49:38 Z executing ssh ... root@172.16.144.21 xl list 2015-10-06 00:49:38 Z guest redhat.guest.osstest state is r 2015-10-06 00:49:38 Z guest redhat.guest.osstest 5a:36:0e:bb:00:3a 22 link/ip/tcp: waiting 100s... 2015-10-06 00:49:52 Z guest redhat.guest.osstest 5a:36:0e:bb:00:3a 22 link/ip/tcp: ping gave (256): PING 172.16.146.215 (172.16.146.215) 56(84) bytes of data. | | --- 172.16.146.215 ping statistics --- | 5 packets transmitted, 0 received, 100% packet loss, time XXXms | | (waiting) ... 2015-10-06 00:49:58 Z guest redhat.guest.osstest 5a:36:0e:bb:00:3a 22 link/ip/tcp: ping gave (256): PING 172.16.146.215 (172.16.146.215) 56(84) bytes of data. | From 172.16.144.3 icmp_seq=1 Destination Host Unreachable | From 172.16.144.3 icmp_seq=2 Destination Host Unreachable | From 172.16.144.3 icmp_seq=3 Destination Host Unreachable | From 172.16.144.3 icmp_seq=4 Destination Host Unreachable | From 172.16.144.3 icmp_seq=5 Destination Host Unreachable | | --- 172.16.146.215 ping statistics --- | 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time XXXms | pipe 3 | (waiting) ... 2015-10-06 00:50:04 Z guest redhat.guest.osstest 5a:36:0e:bb:00:3a 22 link/ip/tcp: ping gave (256): PING 172.16.146.215 (172.16.146.215) 56(84) bytes of data. | From 172.16.144.3 icmp_seq=1 Destination Host Unreachable | From 172.16.144.3 icmp_seq=2 Destination Host Unreachable | From 172.16.144.3 icmp_seq=3 Destination Host Unreachable | From 172.16.144.3 icmp_seq=4 Destination Host Unreachable | From 172.16.144.3 icmp_seq=5 Destination Host Unreachable | | --- 172.16.146.215 ping statistics --- | 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time XXXms | pipe 4 | (waiting) ... 2015-10-06 00:50:09 Z guest redhat.guest.osstest 5a:36:0e:bb:00:3a 22 link/ip/tcp: nc: 256 (UNKNOWN) [172.16.146.215] 22 (ssh) : Connection refused | (waiting) ... 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@172.16.146.215 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@172.16.146.215 echo guest redhat.guest.osstest: ok status (timed out) at Osstest/TestSupport.pm line 410. However http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-i386-qemut-rhel6hvm-amd/ALL.html suggests it is very rare though, much more so than the sshd issue. 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. Ian.