Xen project Mailing List

[Xen-devel] Daily Xen Builds

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>

From: "David F. Barrera" <dfbp@xxxxxxxxxx>

Date: Thu, 18 May 2006 12:59:50 -0500

Delivery-date: Thu, 18 May 2006 11:00:15 -0700

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

May 18, 2006, using xen-unstable changeset: changeset: 10028:25dbb1819633 tag: tip user: kaf24@xxxxxxxxxxxxxxxxxxxx date: Thu May 18 04:43:05 2006 +0100 summary: Remove __TEST_HARNESS__ tests from x86_emulate: instead check for __XEN__ 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:

---------------------+------+------+-------+-------+ hs20.1.sles9-x86_64 | 104 | 11 | 0 | 3 | hs20.rhel4-x86_32pae | 102 | 13 | 0 | 3 | x335fc4pae | 96 | 19 | 0 | 3 | x335sles9_pae4gb | 78 | 37 | 0 | 3 | -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides

Xm-test execution summary: PASS: 104 FAIL: 11 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: 01_enforce_dom0_cpus_basic_pos /proc/cpuinfo says xend didn't enforce dom0_cpus (3 != 1) 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 64 512 1440 65507. FAIL: 07_network_dom0_udp_pos UDP hping2 to dom0 failed for size 48 64 1500 1505 4096 4192. XFAIL: 11_network_domU_ping_pos Ping failed for size 48 64 512 1440 1500 1505 4096 65507. FAIL: 12_network_domU_tcp_pos TCP hping2 failed for size 1440 1500 1505 4096 16384 24567 32767 65495. FAIL: 13_network_domU_udp_pos UDP hping2 failed for size 4096 4192 32767 65495.

Xm-test execution summary: PASS: 102 FAIL: 13 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: 01_enforce_dom0_cpus_basic_pos /proc/cpuinfo says xend didn't enforce dom0_cpus (2 != 1) 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 48 64 512 65507. FAIL: 06_network_dom0_tcp_pos TCP hping2 to dom0 failed for size 48 64 512 1440 1500. FAIL: 07_network_dom0_udp_pos UDP hping2 to dom0 failed for size 1500 1505 4096. XFAIL: 11_network_domU_ping_pos Ping failed for size 32767 65507. FAIL: 12_network_domU_tcp_pos TCP hping2 failed for size 4096 16384 24567 32767 65495. FAIL: 13_network_domU_udp_pos UDP hping2 failed for size 4096 4192 32767 65495.

Xm-test execution summary: PASS: 96 FAIL: 19 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: 09_block_attach_and_dettach_device_check_data_pos Unknown reason FAIL: 01_block-destroy_btblock_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: 15_create_smallmem_pos Unknown reason FAIL: 01_destroy_basic_pos Unknown reason FAIL: 07_destroy_stale_pos Unknown reason FAIL: 01_enforce_dom0_cpus_basic_pos /proc/cpuinfo says xend didn't enforce dom0_cpus (3 != 1) 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 512 1440 65507. FAIL: 07_network_dom0_udp_pos UDP hping2 to dom0 failed for size 48 64 512 1440 1500. XFAIL: 11_network_domU_ping_pos Ping failed for size 64 512 32767 65507. FAIL: 12_network_domU_tcp_pos TCP hping2 failed for size 1505 4096 4192. FAIL: 13_network_domU_udp_pos UDP hping2 failed for size 4096 4192 32767 65495.

Xm-test execution summary: PASS: 78 FAIL: 37 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: 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: 01_destroy_basic_pos Unknown reason FAIL: 07_destroy_stale_pos Unknown reason FAIL: 01_enforce_dom0_cpus_basic_pos /proc/cpuinfo says xend didn't enforce dom0_cpus (3 != 1) FAIL: 01_memset_basic_pos Unknown reason FAIL: 03_memset_random_pos Unknown reason FAIL: 04_memset_smallmem_pos Unknown reason XFAIL: 02_network_local_ping_pos Unknown reason XFAIL: 05_network_dom0_ping_pos Ping to dom0 failed for size 65507. FAIL: 07_network_dom0_udp_pos Unknown reason XFAIL: 11_network_domU_ping_pos Unknown reason FAIL: 12_network_domU_tcp_pos TCP hping2 failed for size 64 512 1440 1500. FAIL: 13_network_domU_udp_pos UDP hping2 failed for size 512 1440 1500 1505 65495. FAIL: 02_network_attach_detach_pos Unknown reason FAIL: 03_network_attach_detach_multiple_pos Unknown reason FAIL: 01_pause_basic_pos Unknown reason FAIL: 01_restore_basic_pos Unknown reason FAIL: 04_restore_withdevices_pos Unknown reason FAIL: 03_save_bogusfile_neg Unknown reason FAIL: 01_shutdown_basic_pos Unknown reason FAIL: 02_sysrq_sync_pos Unknown reason FAIL: 01_unpause_basic_pos Unknown reason

_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.