diff -r d409f1d12edd -r bc36b82c6bd0 suites/libvirt-cim/cimtest/LogicalDisk/03_ld_gi_errs.py --- a/suites/libvirt-cim/cimtest/LogicalDisk/03_ld_gi_errs.py Wed Sep 03 22:54:35 2008 -0700 +++ b/suites/libvirt-cim/cimtest/LogicalDisk/03_ld_gi_errs.py Thu Sep 04 23:28:28 2008 -0700 @@ -123,6 +123,7 @@
diff -r d409f1d12edd -r bc36b82c6bd0 suites/libvirt-cim/cimtest/Memory/01_memory.py --- a/suites/libvirt-cim/cimtest/Memory/01_memory.py Wed Sep 03 22:54:35 2008 -0700 +++ b/suites/libvirt-cim/cimtest/Memory/01_memory.py Thu Sep 04 23:28:28 2008 -0700
diff -r d409f1d12edd -r bc36b82c6bd0 suites/libvirt-cim/cimtest/NetworkPort/01_netport.py --- a/suites/libvirt-cim/cimtest/NetworkPort/01_netport.py Wed Sep 03 22:54:35 2008 -0700 +++ b/suites/libvirt-cim/cimtest/NetworkPort/01_netport.py Thu Sep 04 23:28:28 2008 -0700
diff -r d409f1d12edd -r bc36b82c6bd0 suites/libvirt-cim/cimtest/RASD/02_enum.py --- a/suites/libvirt-cim/cimtest/RASD/02_enum.py Wed Sep 03 22:54:35 2008 -0700 +++ b/suites/libvirt-cim/cimtest/RASD/02_enum.py Thu Sep 04 23:28:28 2008 -0700
diff -r d409f1d12edd -r bc36b82c6bd0 suites/libvirt-cim/cimtest/ResourceAllocationFromPool/01_forward.py --- a/suites/libvirt-cim/cimtest/ResourceAllocationFromPool/01_forward.py Wed Sep 03 22:54:35 2008 -0700 +++ b/suites/libvirt-cim/cimtest/ResourceAllocationFromPool/01_forward.py Thu Sep 04 23:28:28 2008 -0700
diff -r d409f1d12edd -r bc36b82c6bd0 suites/libvirt-cim/cimtest/ResourceAllocationFromPool/05_RAPF_err.py --- a/suites/libvirt-cim/cimtest/ResourceAllocationFromPool/05_RAPF_err.py Wed Sep 03 22:54:35 2008 -0700 +++ b/suites/libvirt-cim/cimtest/ResourceAllocationFromPool/05_RAPF_err.py Thu Sep 04 23:28:28 2008 -0700
All of these tests fail with Xen and XenFV due to the libvirt caching issue. Instead of adding a 10 second delay, I think it's possible to get around the caching issue by changing the define() call to cim_define(). Can you see if cim_define() works for you? Thanks! -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com