From mboxrd@z Thu Jan 1 00:00:00 1970 From: David F Barrera Subject: Re: Daily Xen Builds Date: Mon, 12 Jun 2006 14:49:52 -0500 Message-ID: <448DC560.8080609@us.ibm.com> References: <448DB50C.8030000@us.ibm.com> <448DBFF8.1000104@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <448DBFF8.1000104@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Liguori Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Anthony Liguori wrote: > David F Barrera wrote: >> June 12, 2006, using xen-unstable changeset: >> >> changeset: 10326:34ff26fb2240 >> tag: tip >> user: kaf24@firebug.cl.cam.ac.uk >> date: Mon Jun 12 06:01:32 2006 +0100 >> summary: [HVM][VMX] Fix error-detection inline asm code. Zero >> word-sized >> >> x86_32 (no PAE support) >> >> * SLES 9 SP2 on IBM xSeries 235(512MB RAM) >> * Builds and boots without problems >> * Ran xm-test on all boxes >> >> ISSUES: >> >> Note: these problems are due to the way xm-test works, rather than >> xen problems. >> * Bugzilla 637 NEW xm-test FAIL: 01_block_attach_device_pos.test >> * Bugzilla 639 NEW xm-test multiple test failures - >> >> x86_32 (PAE) >> >> * SLES 9 SP2 on xSeries 335 and HS20 Blade 8843and FC4 on IBM xSeries >> 335s * Builds and boots without problems >> * Ran xm-test on all boxes >> >> ISSUES: >> * Bugzilla 637 NEW xm-test FAIL: 01_block_attach_device_pos.test >> * Bugzilla 639 NEW xm-test multiple test failures - >> XmTestLib.Console.Consol... >> >> x86_64 (SLES 9 SP2 IBM HS20 Blades 8843 41U) >> >> * Builds and boots without problems >> * Ran xm-test on all boxes >> >> ISSUES: >> >> XM-TEST Results : >> Platform | PASS | FAIL | XPASS | XFAIL | >> ---------------------+------+------+-------+-------+ >> hs20.1.sles9-x86_64 | 109 | 8 | 0 | 3 | >> hs20.rhel14-x86 | 76 | 40 | 0 | 3 | >> x235sles9nonpae | 70 | 47 | 0 | 3 | >> x335fc4pae | 83 | 34 | 0 | 3 | >> x335sles9_pae4gb | 93 | 23 | 0 | 3 | > > I'm not sure what's happening on your systems, but on my development > system (i386 Ubuntu), I'm seeing only a few unexpected FAILs. I've > run xm-test about a dozen times on the recent tip with more or less > consistent results (including with the new scheduler). Perhaps > there's something wrong in your setup? > > Attached is a canonical example of one of the recent xm-test reports. > > Regards, > > Anthony Liguori > > ------------------------------------------------------------------------ > > Xm-test execution summary: > PASS: 108 > FAIL: 7 > XPASS: 0 > XFAIL: 3 > > > Details: > > FAIL: 02_block_device_write_verify > Failed to get md5sum of data written in domU. > > FAIL: 16_create_smallmem_neg > Starting a console with 16 MB passed, expected test to fail > > XFAIL: 02_network_local_ping_pos > ping loopback failed for size 65507. ping eth0 failed for size 65507. > > XFAIL: 05_network_dom0_ping_pos > Ping to dom0 failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65507. > > FAIL: 06_network_dom0_tcp_pos > TCP hping2 to dom0 failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65495. > > FAIL: 07_network_dom0_udp_pos > UDP hping2 to dom0 failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65495. > > XFAIL: 11_network_domU_ping_pos > Ping failed for size 65507. > > Here's a snippet of one test (multiply this many times): *** Test 14_create_blockroot_pos started at Mon Jun 12 07:04:21 2006 CDT [dom0] Running `ip addr show |grep "inet 169.254" | grep -v vif' [dom0] Running `ip addr show dev vif0.0' 2: vif0.0: mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet 169.254.0.2/32 scope global vif0.0 inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever [dom0] Running `ip addr del 169.254.0.2 dev vif0.0' *** Cleaning all running domU's [dom0] Running `xm list' Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 500 4 r----- 693.3 *** Finished cleaning domUs *** Test 14_create_blockroot_pos started at Mon Jun 12 07:04:22 2006 CDT [dom0] Running `ip addr show |grep "inet 169.254" | grep -v vif' [dom0] Running `ip addr show dev vif0.0' 2: vif0.0: mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever [dom0] Running `xm create /tmp/xm-test.conf' Using config file "/tmp/xm-test.conf". Started domain 14_create_blockroot Console executing: ['/usr/sbin/xm', 'xm', 'console', '14_create_blockroot'] [14_create_blockroot] Sending `input' Traceback (most recent call last): File "./14_create_blockroot_pos.test", line 34, in ? console = domain.start() File "/usr/local/autobench/var/tmp/xen/xen-unstable.hg/tools/xm-test/lib/XmTestLib/XenDomain.py", line 233, in start return self.getConsole() File "/usr/local/autobench/var/tmp/xen/xen-unstable.hg/tools/xm-test/lib/XmTestLib/XenDomain.py", line 284, in getConsole self.console.sendInput("input") File "/usr/local/autobench/var/tmp/xen/xen-unstable.hg/tools/xm-test/lib/XmTestLib/Console.py", line 231, in sendInput realOutput = self.__runCmd(input) File "/usr/local/autobench/var/tmp/xen/xen-unstable.hg/tools/xm-test/lib/XmTestLib/Console.py", line 179, in __runCmd raise ConsoleError("Timed out waiting for console") XmTestLib.Console.ConsoleError: Timed out waiting for console FAIL: 14_create_blockroot_pos.test -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides