From: Rick Gonzalez <rcgneo@us.ibm.com>
To: Xen Developers <xen-devel@lists.xensource.com>
Subject: Daily Xen-HVM Build Testing: cs10482: 64bit xm-test problems
Date: Tue, 27 Jun 2006 10:45:21 -0500 [thread overview]
Message-ID: <44A15291.305@us.ibm.com> (raw)
changeset: 10482:9ec0b4f10b4f
tag: tip
user: emellor@leeni.uk.xensource.com
date: Sat Jun 24 17:44:18 2006 +0100
summary: Some fine-tuning in the virtual TPM scripts for hotpluging.
The changes
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
ISSUES:
* 3 fails on xm-test.
SUMMARY:
Xm-test execution summary:
PASS: 68
FAIL: 3
XPASS: 2
XFAIL: 1
Details:
FAIL: 11_create_concurrent_pos
[11] Failed to attach console to 11_create_11
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.
--- Windows HVM domain status: ---
* I'll get to testing the other Windowns OS when I automate the test cases.
+------------------------------------+
| Test | OS |
| Category |-----------------------|
| | Win2k| Win2k3 | WinXP |
+------------------------------------+
| Networking | | | pass |
| Graphics | | | pass |
| Disk I/O | | | pass |
| Xen | | | N/A |
+------------------------------------+
ISSUES:
None
********************** x86_64: *********************************
* dom0: SLES9 SP2
* dom0 boots fine
* xend starts without problems
--- Linux HVM domain status: ---
* Xm-test completes
* Able to boot multiple HVM domains
ISSUES:
* 22 xm-tests failing
SUMMERY:
Xm-test execution summary:
PASS: 49
FAIL: 22
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_create_basic_pos
Unknown reason
FAIL: 11_create_concurrent_pos
Unknown reason
FAIL: 12_create_concurrent_stress_pos
Unknown reason
FAIL: 13_create_multinic_pos
Unknown reason
FAIL: 14_create_blockroot_pos
Unknown reason
FAIL: 15_create_smallmem_pos
Unknown reason
FAIL: 01_destroy_basic_pos
Unknown reason
FAIL: 07_destroy_stale_pos
Unknown reason
FAIL: 04_list_goodparm_pos
Unknown reason
XFAIL: 02_network_local_ping_pos
Unknown reason
FAIL: 03_network_local_tcp_pos
Unknown reason
FAIL: 04_network_local_udp_pos
Unknown reason
XFAIL: 05_network_dom0_ping_pos
Unknown reason
FAIL: 06_network_dom0_tcp_pos
Unknown reason
FAIL: 07_network_dom0_udp_pos
Unknown reason
XFAIL: 11_network_domU_ping_pos
Unknown reason
FAIL: 12_network_domU_tcp_pos
Unknown reason
FAIL: 13_network_domU_udp_pos
Unknown reason
FAIL: 01_pause_basic_pos
Unknown reason
FAIL: 01_reboot_basic_pos
Unknown reason
FAIL: 01_shutdown_basic_pos
Unknown reason
FAIL: 01_unpause_basic_pos
Unknown reason
--- Windows HVM domain status: ---
+------------------------------------+
| Test | OS |
| Category |-----------------------|
| | Win2k| Win2k3 | WinXP |
+------------------------------------+
| Networking | | | N/A |
| Graphics | | | N/A |
| Disk I/O | | | N/A |
| Xen | | | N/A |
+------------------------------------+
ISSUES:
none
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
reply other threads:[~2006-06-27 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44A15291.305@us.ibm.com \
--to=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.