From: David F Barrera <dfbp@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Daily Xen Buillds
Date: Tue, 23 May 2006 12:56:15 -0500 [thread overview]
Message-ID: <44734CBF.6000707@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
May 23, 2006, using xen-unstable changeset:
changeset: 10068:13d6d993d797
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Mon May 22 11:30:25 2006 +0100
summary: [IA64] Work around auto-ballooning changes.
x86_32 (no PAE support)
* SLES 9 SP2 on IBM xSeries 235(512MB RAM)
* Builds and boots without problems
* Able to create fully functional guest domains
* 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...
Note: test logs attached to defects in Xensource Bugzilla.
x86_32 (PAE)
* SLES 9 SP2 on xSeries 335 and HS20 Blade 8843and FC4 on IBM xSeries 335s
* Builds and boots without problems
* Able to create fully functional guest domains
* 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
* Able to create fully functional guest domains
* Ran xm-test on all boxes
ISSUES:
================
XM-TEST Results:
Platform | PASS | FAIL | XPASS | XFAIL |
---------------------+------+------+-------+-------+
hs20.1.sles9-x86_64 | 106 | 9 | 0 | 3 |
hs20.rhel4-x86_32pae | 106 | 9 | 0 | 3 |
x235sles9nonpae | 73 | 39 | 0 | 3 |
x335sles9_pae4gb | 75 | 40 | 0 | 3 |
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
[-- Attachment #2: hs20.rhel4-x86_32pae.report --]
[-- Type: text/plain, Size: 877 bytes --]
Xm-test execution summary:
PASS: 106
FAIL: 9
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_block_attach_device_pos
block-attach failed device did not switch to Connected state
FAIL: 02_block_attach_file_device_pos
block-attach failed device did not switch to Connected state
FAIL: 04_block_attach_device_repeatedly_pos
Device is not actually attached to domU
FAIL: 05_block_attach_and_dettach_device_repeatedly_pos
block-attach failed device did not switch to Connected state
FAIL: 03_memset_random_pos
Timed out waiting for console
FAIL: 01_migrate_localhost_pos
xm migrate returned invalid 256 != 0
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 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 65507.
[-- Attachment #3: hs20.1.sles9-x86_64.report --]
[-- Type: text/plain, Size: 901 bytes --]
Xm-test execution summary:
PASS: 106
FAIL: 9
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_block_attach_device_pos
block-attach failed device did not switch to Connected state
FAIL: 02_block_attach_file_device_pos
block-attach failed device did not switch to Connected state
FAIL: 04_block_attach_device_repeatedly_pos
Device is not actually attached to domU
FAIL: 05_block_attach_and_dettach_device_repeatedly_pos
block-attach failed device did not switch to Connected state
FAIL: 03_memset_random_pos
Timed out waiting for console
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 65507.
FAIL: 07_network_dom0_udp_pos
UDP hping2 to dom0 failed for size 512 1440 1500 32767 65495.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 65507.
[-- Attachment #4: x335sles9_pae4gb.report --]
[-- Type: text/plain, Size: 2259 bytes --]
Xm-test execution summary:
PASS: 75
FAIL: 40
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_block_attach_device_pos
FAIL: 02_block_attach_file_device_pos
block-attach failed device did not switch to Connected state
FAIL: 04_block_attach_device_repeatedly_pos
Unknown reason
FAIL: 05_block_attach_and_dettach_device_repeatedly_pos
Unknown reason
FAIL: 08_block_attach_bad_filedevice_neg
Unknown reason
FAIL: 09_block_attach_and_dettach_device_check_data_pos
Unknown reason
FAIL: 12_block_attach_shared_domU
Unknown reason
FAIL: 01_block-destroy_btblock_pos
Unknown reason
FAIL: 02_block-destroy_rtblock_pos
Unknown reason
FAIL: 05_block-destroy_byname_pos
Unknown reason
FAIL: 01_block-list_pos
Unknown reason
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: 07_destroy_stale_pos
Unknown reason
FAIL: 04_list_goodparm_pos
Unknown reason
FAIL: 01_memset_basic_pos
Unknown reason
FAIL: 03_memset_random_pos
Unknown reason
FAIL: 04_memset_smallmem_pos
Unknown reason
FAIL: 01_migrate_localhost_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
Ping to dom0 failed for size 65507.
FAIL: 06_network_dom0_tcp_pos
Unknown reason
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1505 4096 32767 65507.
FAIL: 12_network_domU_tcp_pos
TCP hping2 failed for size 4096 4192 16384 24567.
FAIL: 13_network_domU_udp_pos
Unknown reason
FAIL: 03_network_attach_detach_multiple_pos
Unknown reason
FAIL: 01_reboot_basic_pos
Unknown reason
FAIL: 01_restore_basic_pos
Unknown reason
FAIL: 04_restore_withdevices_pos
Unknown reason
FAIL: 01_save_basic_pos
Unknown reason
FAIL: 03_save_bogusfile_neg
Unknown reason
FAIL: 01_shutdown_basic_pos
Unknown reason
FAIL: 03_sysrq_withreboot_pos
Unknown reason
FAIL: 01_unpause_basic_pos
Unknown reason
[-- Attachment #5: x235sles9nonpae.report --]
[-- Type: text/plain, Size: 2157 bytes --]
Xm-test execution summary:
PASS: 73
FAIL: 39
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_block_attach_device_pos
FAIL: 02_block_attach_file_device_pos
Unknown reason
FAIL: 04_block_attach_device_repeatedly_pos
Unknown reason
FAIL: 05_block_attach_and_dettach_device_repeatedly_pos
Unknown reason
FAIL: 07_block_attach_baddevice_neg
Unknown reason
FAIL: 08_block_attach_bad_filedevice_neg
Unknown reason
FAIL: 09_block_attach_and_dettach_device_check_data_pos
Unknown reason
FAIL: 12_block_attach_shared_domU
Unknown reason
FAIL: 01_block-destroy_btblock_pos
Unknown reason
FAIL: 02_block-destroy_rtblock_pos
Unknown reason
FAIL: 05_block-destroy_byname_pos
Unknown reason
FAIL: 06_block-destroy_check_list_pos
Unknown reason
FAIL: 01_block-list_pos
Unknown reason
FAIL: 02_block-list_attachbd_pos
Unknown reason
FAIL: 03_block-list_anotherbd_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: 01_destroy_basic_pos
Unknown reason
FAIL: 07_destroy_stale_pos
Unknown reason
FAIL: 04_list_goodparm_pos
Unknown reason
FAIL: 03_memset_random_pos
Unknown reason
FAIL: 01_migrate_localhost_pos
Unknown reason
XFAIL: 02_network_local_ping_pos
Unknown reason
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 4096 4192 32767 65507.
FAIL: 06_network_dom0_tcp_pos
Unknown reason
FAIL: 07_network_dom0_udp_pos
UDP hping2 to dom0 failed for size 32767 65495.
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: 02_network_attach_detach_pos
Unknown reason
FAIL: 01_pause_basic_pos
Unknown reason
FAIL: 01_reboot_basic_pos
Unknown reason
FAIL: 04_restore_withdevices_pos
Unknown reason
FAIL: 01_save_basic_pos
Unknown reason
FAIL: 01_shutdown_basic_pos
Unknown reason
FAIL: 02_sysrq_sync_pos
Unknown reason
FAIL: 03_sysrq_withreboot_pos
Unknown reason
FAIL: 01_unpause_basic_pos
Unknown reason
[-- Attachment #6: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2006-05-23 17:56 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=44734CBF.6000707@us.ibm.com \
--to=dfbp@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.