Re: [Libvirt-cim] XenFV on Pegasus Test Run Summary for Aug 28 2008
All the above tc failed since the RegisteredProfile ,
ElementConformsToProfile and ReferencedProfile were not registered in
the interop namespace.
I registered the above classes manually by running :
sh provider-register.sh -v -t pegasus -n root/interop -r
schema/RegisteredProfile.registration
schema/ElementConformsToProfile.registration
schema/ReferencedProfile.registration -m schema/ComputerSystem.mof
schema/HostSystem.mof schema/RegisteredProfile.mof
schema/ElementConformsToProfile.mof schema/ReferencedProfile.mof
I'd thought this issue was fixed. Did you run a make preinstall before
running make install && make postinstall?
>
--------------------------------------------------------------------
> ElementConforms - 03_ectp_fwd_errs.py: FAIL
> Traceback (most recent call last):
> File "/usr/lib64/python2.4/logging/__init__.py", line 731, in emit
> msg = self.format(record)
> File "/usr/lib64/python2.4/logging/__init__.py", line 617, in format
> return fmt.format(record)
> File "/usr/lib64/python2.4/logging/__init__.py", line 405, in format
> record.message = record.getMessage()
> File "/usr/lib64/python2.4/logging/__init__.py", line 276, in
>
--------------------------------------------------------------------
> Profile - 03_rprofile_gi_errs.py: FAIL
> Traceback (most recent call last):
> File "/usr/lib64/python2.4/logging/__init__.py", line 731, in emit
> msg = self.format(record)
> File "/usr/lib64/python2.4/logging/__init__.py", line 617, in format
> return fmt.format(record)
> File "/usr/lib64/python2.4/logging/__init__.py", line 405, in format
> record.message = record.getMessage()
> File "/usr/lib64/python2.4/logging/__init__.py", line 276, in
> getMessage
Even if these tests fail, they shouldn't dump Python messages like this.
Do you know if these tests aren't trapping an exception of some sort
properly?
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com