From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [xen-4.2-testing test] 19031: regressions - FAIL Date: Wed, 4 Sep 2013 10:50:55 -0400 Message-ID: <20130904145055.GE3188@phenom.dumpdata.com> References: <522707A102000078000F03CE@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VHEQC-00014L-HZ for xen-devel@lists.xenproject.org; Wed, 04 Sep 2013 14:51:04 +0000 Content-Disposition: inline In-Reply-To: <522707A102000078000F03CE@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel , ian.jackson@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On Wed, Sep 04, 2013 at 09:12:49AM +0100, Jan Beulich wrote: > >>> On 04.09.13 at 07:17, xen.org wrote: > > flight 19031 xen-4.2-testing real [real] > > http://www.chiark.greenend.org.uk/~xensrcts/logs/19031/ > > > > Regressions :-( > > > > Tests which did not succeed and are blocking, > > including tests which could not be run: > > test-amd64-i386-xend-qemut-winxpsp3 7 windows-install fail REGR. vs. 18801 > > So the stable trees are apparently using the 3.10-based kernels > too, and woodlouse is giving a problem there too. Which hints > even more strongly at a kernel side problem on that specific box > than a regression in recent -unstable commits. Which in turn > raises the question of how to best get -unstable's staging tree's > backlog taken care of, alongside the question of how to get > pushes on the soon-to-be-released stable trees. It is interesting that it fails at the same problem the linux-real had been failing. That is when doing rsync. 5120 bytes (5.1 kB) copied, 0.0194138 s, 264 kB/s 2013-09-04 04:42:13 Z execution took 19 seconds [**>30/2**]: 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_19031.test-amd64-i386-xend-qemut-winxpsp3 root@10.80.248.105 dd if=/dev/zero of=/dev/woodlouse/win.guest.osstest-disk count=10 2013-09-04 04:42:13 Z executing rsync ... -p /home/xc_osstest/images/winxpsp3.iso root@10.80.248.105:/root/19031.test-amd64-i386-xend-qemut-winxpsp3.winxpsp3.iso 2013-09-04 04:58:53 Z command timed out [1000]: rsync -e 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_19031.test-amd64-i386-xend-qemut-winxpsp3 -p /home/xc_osstest/images/winxpsp3.iso root@10.80.248.105:/root/19031.test-amd64-i386-xend-qemut-winxpsp3.winxpsp3.iso status (timed out) at Osstest/TestSupport.pm line 375. + rc=4 + date -u '+%Y-%m-%d %H:%M:%S Z exit status 4' 2013-09-04 04:58:53 Z exit status 4 + exit 4 rsync error: unexplained error (code 143) at rsync.c(541) [sender=3.0.3] Ian, is it possible to a bit more verbose - perhaps that will shed some light at this awful speed. There does not seem to be anything about the 'tg3' blowing up? Ian, would it also be able to get the interrupt count _Before_ and _after_ the timeout? Perhaps the interrupts aren't going to the device? Thanks. > > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel