[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-unstable test] 22283: regressions - FAIL
On Wed, 2013-12-04 at 19:13 +0000, xen.org wrote: > flight 22283 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/22283/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > build-armhf 4 xen-build fail REGR. vs. > 22278 > build-armhf-pvops 4 kernel-build fail REGR. vs. > 22278 > build-amd64-pvops 4 kernel-build fail REGR. vs. > 22278 > build-amd64 4 xen-build fail REGR. vs. > 22278 > build-amd64-oldkern 4 xen-build fail REGR. vs. > 22278 The amd64 ones are all: Warning: Permanently added '10.80.249.149' (RSA) to the list of known hosts. 2013-12-04 17:47:08 Z command timed out [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_22283.build-amd64 osstest@xxxxxxxxxxxxx rm -rf /home/osstest/build.22283.build-amd64 && mkdir /home/osstest/build.22283.build-amd64 status (timed out) at Osstest/TestSupport.pm line 379. Same IP in every case. Looks like gall-mite had an episode: Dec 4 16:21:31.216425 gall-mite login: [ 481.242300] INFO: task kjournald:370 blocked for more than 120 seconds. Dec 4 16:29:06.956848 [ 481.248975] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Dec 4 16:29:06.964750 [ 481.256985] INFO: task rs:main Q:Reg:20255 blocked for more than 120 seconds. The armhf ones are: 2013-12-04 17:45:01 Z executing ssh ... osstest@xxxxxxxxxxxx rm -rf /local/scratch/osstest/osstest/build.22283.build-armhf && mkdir /local/scratch/osstest/osstest/build.22283.build-armhf Warning: Permanently added '10.80.246.74' (RSA) to the list of known hosts. mkdir: cannot create directory `/local/scratch/osstest/osstest/build.22283.build-armhf': No such file or directory 2013-12-04 17:45:02 Z command nonzero waitstatus 256: 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_22283.build-armhf osstest@xxxxxxxxxxxx rm -rf /local/scratch/osstest/osstest/build.22283.build-armhf && mkdir /local/scratch/osstest/osstest/build.22283.build-armhf status 256 at Osstest/TestSupport.pm line 379. The host is army and: $ ls /local/scratch/osstest/osstest/ build.22298.build-armhf/ build.22299.build-armhf/ build.22298.build-armhf-pvops/ build.22299.build-armhf-pvops/ plus sudo su -c 'mkdir /local/scratch/osstest/osstest/build.22283.build-armhf' osstest works. so I'm a bit perplexed by this one. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |