Re: [Libvirt-cim] cimtest results.

"Eduardo Lima (Etrunko)" <eblima(a)linux.vnet.ibm.com&gt; 10/27/2011 05:17 AM Please respond to eblima(a)br.ibm.com To Sharad Mishra/Beaverton/IBM@IBMUS cc eblima(a)br.ibm.com, Chip Vincent/Raleigh/IBM@IBMUS, wayne <xiawenc(a)linux.vnet.ibm.com&gt;, Gareth S Bestor/Poughkeepsie/IBM@IBMUS Subject Re: cimtest results. On 10/26/2011 08:07 PM, snmishra(a)us.ibm.com wrote: > Hi, > > I see bunch of tests failing after I get cimtest from upstream and

> the following patches - > > https://www.redhat.com/archives/libvirt-cim/2011-October/msg00051.html > https://www.redhat.com/archives/libvirt-cim/2011-October/msg00052.html > https://www.redhat.com/archives/libvirt-cim/2011-October/msg00045.html > > > If I run cimtest from rev 879 (which is upstream minus latest 4

> and compare the results with the run using latest upstream plus above > three patches I see following extra failures - > > VirtualSystemManagementService - 08_modifyresource.py: FAIL > VirtualSystemManagementService - 09_procrasd_persist.py: FAIL > VirtualSystemManagementService - 11_define_memrasdunits.py: FAIL > VirtualSystemManagementService - 31_unset_netrasd.py: FAIL > VirtualSystemManagementService - 32_modify_cdrom_media.py: FAIL > KVMRedirectionSAP - 01_enum_KVMredSAP.py: FAIL > > I understand that 31_* and 32_* are new tests and that is the reason I > did not see them in my run with older rev. But we need to figure out

> these tests are failing. > The buggy patch is 883 ([TEST] XenKvmLib: Add cdrom device description to domain) and it looks weird that you actually ran revision 879 as it should not include VSMS 31 and 32. Can you try again with revision 882?

Best regards, Etrunko -- Eduardo de Barros Lima Software Engineer, Open Virtualization Linux Technology Center - IBM/Brazil eblima(a)br.ibm.com