From: David F Barrera <dfbp@us.ibm.com>
To: Rick Gonzalez <rcgneo@us.ibm.com>
Cc: Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: Daily Xen-HVM Build Testing: cs10946
Date: Fri, 04 Aug 2006 15:26:54 -0500 [thread overview]
Message-ID: <44D3AD8E.1030701@us.ibm.com> (raw)
In-Reply-To: <44D39C79.1050703@us.ibm.com>
Rick Gonzalez wrote:
> changeset: 10946:e1a2a8029e9f
> tag: tip
> user: chris@kneesaa.uk.xensource.com
> date: Fri Aug 4 05:36:07 2006 +0100
> summary: [qemu patches] Update patches for changeset
> 10945:baa6d08e62a0.
>
>
>
> Hardware: x460
>
> ******************** x86_32(no PAE): ***************************
>
> * dom0: SLES9 SP2
> * dom0 boots fine
> * xend starts without problem
>
> --- Linux HVM domain status: ---
>
> * Xm-test completes.
> * Able to boot multiple HVM domains
> * Harry B. has a fix for defect 709 and that is how xm-test ran to
> complition this time.
It's 'completion':-)
>
> ISSUES:
>
> * 11 fails on xm-test.
>
> SUMMARY:
> Xm-test execution summary:
> PASS: 60
> FAIL: 11
> XPASS: 0
> XFAIL: 3
>
>
> Details:
>
> FAIL: 11_create_concurrent_pos
> [15] Failed to create domain
>
> 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
> 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
>
> FAIL: 03_network_local_tcp_pos
> TCP hping2 over eth0 failed for size 1 48 64 512 1440 1448
> 1500 1505 4096 4192 32767 65495.
>
> FAIL: 04_network_local_udp_pos
> UDP hping2 over eth0 failed for size 1 48 64 512 1440 1448
> 1500 1505 4096 4192 32767 65495.
>
> 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 1 48 64 512 1440 1500 1505 4096 4192
> 32767 65507.
>
> FAIL: 12_network_domU_tcp_pos
> TCP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
> 4192 16384 24567 32767 65495.
>
> FAIL: 13_network_domU_udp_pos
> UDP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
> 4192 32767 65495.
>
>
> --- Windows HVM domain status: ---
>
> * At this time I don't have time to test windows. Windows testing will
> be done weekly instead.
>
> +------------------------------------+
> | Test | OS |
> | Category |-----------------------|
> | | Win2k| Win2k3 | WinXP |
> +------------------------------------+
> | Boot | | | |
> | Networking | | | |
> | Graphics | | | |
> | Disk I/O | | | |
> +------------------------------------+
>
> ISSUES:
>
> None
>
> ********************** x86_64: *********************************
>
> * dom0: SLES10 GM
> * dom0 boots fine
> * xend starts without problems
>
> --- Linux HVM domain status: ---
>
> * Xm-test completes
> * Able to boot multiple HVM domains
>
> ISSUES:
>
> * 11 xm-tests failing
> * Harry B. has a fix for defect 709 and that is how xm-test ran to
> complition this time.
>
> SUMMERY:
>
> Xm-test execution summary:
> PASS: 60
> FAIL: 11
> XPASS: 0
> XFAIL: 3
>
>
> Details:
>
> FAIL: 11_create_concurrent_pos
> [15] Failed to create domain
>
> 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
> 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
>
> FAIL: 03_network_local_tcp_pos
> TCP hping2 over eth0 failed for size 1 48 64 512 1440 1448
> 1500 1505 4096 4192 32767 65495.
>
> FAIL: 04_network_local_udp_pos
> UDP hping2 over eth0 failed for size 1 48 64 512 1440 1448
> 1500 1505 4096 4192 32767 65495.
>
> 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 1 48 64 512 1440 1500 1505 4096 4192
> 32767 65507.
>
> FAIL: 12_network_domU_tcp_pos
> TCP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
> 4192 16384 24567 32767 65495.
>
> FAIL: 13_network_domU_udp_pos
> UDP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
> 4192 32767 65495.
>
> --- Windows HVM domain status: ---
>
>
> * At this time I don't have time to test windows. Windows testing will
> be done weekly instead.
>
> +------------------------------------+
> | Test | OS |
> | Category |-----------------------|
> | | Win2k| Win2k3 | WinXP |
> +------------------------------------+
> | Boot | | | n/a |
> | Networking | | | n/a |
> | Graphics | | | n/a |
> | Disk I/O | | | n/a |
> | Xen | | | n/a |
> +------------------------------------+
>
>
> ISSUES:
>
> NOTE: Contact me if you would like to see all the output files.
>
>
>
> regards,
>
>
>
> ------------------------
> Rick Gonzalez
> Linux Technology Center
> IBM Corporation
> Phone#: 512-838-0623
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
prev parent reply other threads:[~2006-08-04 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 19:14 Daily Xen-HVM Build Testing: cs10946 Rick Gonzalez
2006-08-04 20:26 ` David F Barrera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44D3AD8E.1030701@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=rcgneo@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.