From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Rick Gonzalez <rcgneo@us.ibm.com>
Cc: Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: Daily Xen-HVM Build Testing: cs11011
Date: Fri, 11 Aug 2006 11:00:05 +0100 [thread overview]
Message-ID: <1155290406.7740.3.camel@localhost.localdomain> (raw)
In-Reply-To: <44DB498F.70509@us.ibm.com>
The behaviour of the xm-test code with and without my patch its to pick
a kernel from /boot to test with. For the 32 bit tests below I think
the failures are from picking a bigsmp kernel which AFAIK isn't
supported under 32 bit xen for HVM. I'm not sure about the failures in
the 64bit case.
I'm thinking about adding a kernel build target to the xen build process
to build a kernel for use as a default by xm-test for HVM testing. Does
anyone have any thoughts about this?
I'm away on vacation for a couple of weeks now.
Harry.
On Thu, 2006-08-10 at 09:58 -0500, Rick Gonzalez wrote:
> changeset: 11011:b60ea69932b1
> tag: tip
> parent: 11010:e4f1519b473f
> parent: 10999:15304ad81c50
> user: kfraser@localhost.localdomain
> date: Wed Aug 9 12:04:20 2006 +0100
> summary: Merge with xenppc-unstable.
>
>
>
> Hardware: x460
>
> NOTE: This runs were done with the latest version of Harry's disk.iso patch.
>
> ******************** x86_32(no PAE): ***************************
>
> * dom0: SLES10 GM
> * dom0 boots fine
> * xend starts without problem
>
> --- Linux HVM domain status: ---
>
> * Xm-test completes.
> * Able to boot multiple HVM domains
>
> ISSUES:
>
> * 22 fails on xm-test.dd
>
> SUMMARY:
>
> 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: ---
>
> * These are sniff tests only
>
> +------------------------------------+
> | Test | OS |
> | Category |-----------------------|
> | | Win2k| Win2k3 | WinXP |
> +------------------------------------+
> | Boot | | | Pass |
> | Networking | | | Pass |
> | Graphics | | | Pass |
> | Disk I/O | | | Pass |
> +------------------------------------+
>
> ISSUES:
>
> * There is a little problem with the graphics. There are random squares
> in the SDL window. This was not the case before. This problem is not bad
> but it is a problem.
>
> 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:
>
> * 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: ---
>
>
> * These are sniff tests only.
>
> +------------------------------------+
> | Test | OS |
> | Category |-----------------------|
> | | Win2k| Win2k3 | WinXP |
> +------------------------------------+
> | Boot | | | Pass |
> | Networking | | | Pass |
> | Graphics | | | Pass |
> | Disk I/O | | | Pass |
> +------------------------------------+
>
>
> ISSUES:
>
> * There is a little problem with the graphics. There are random squares
> in the SDL window. This was not the case before. This problem is not bad
> but it is a problem.
>
> 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
prev parent reply other threads:[~2006-08-11 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 14:58 Daily Xen-HVM Build Testing: cs11011 Rick Gonzalez
2006-08-11 10:00 ` Harry Butterworth [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=1155290406.7740.3.camel@localhost.localdomain \
--to=harry@hebutterworth.freeserve.co.uk \
--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.