[Libvirt-cim] Test report on KVM

[Guo Lian Yun]

libvirt-cim-bounces at redhat.com wrote on 2008-04-05 04:59:59:

> Hi all,
>
> Today I ran a full test run against my local machine in KVM mode (with
> "-v KVM").  Things look pretty good, and I think most of the failures
> are likely to be test-related and not necessarily provider-related.
>
  Did you run it on elm3b197.beaverton.ibm.com in KVM mode? I ran it
  on your machine(elm3b197.beaverton.ibm.com) in KVM mode and add
  comments inline.

> For those of you working on the test suite, I'd appreciate it if you
> could look through these and figure out what the issues are.
>
> Thanks!
>
> --
> Dan Smith
> IBM Linux Technology Center
> Open Hypervisor Team
> email: danms at us.ibm.com
>
> > ElementCapabilities - 01_forward.py: FAIL
> > CIM_ERR_NOT_FOUND: The requested object could not be found: "No
> such instance (CreationClassName)"
   It passed during my test.

> > ElementCapabilities - 05_hostsystem_cap.py: FAIL
> > CIM_ERR_NOT_FOUND: The requested object could not be found: "No
> such instance"
>
   It fails because of missing argument, I fixed it already.

> This looks like a test case error that is failing to provide a key
>
> > ElementConforms - 01_forward.py: FAIL
> > ElementConforms - 02_reverse.py: FAIL
>
> The log:
>
> > ====01_forward.py Log====
> > 1. Property values for CIM:DSP1057-VirtualSystem-1.0.0a and domain
> Domain-0 is
> > EnabState = 2 EnabDefault = 2 ReqSt = 12
> > 2. Values for CIM:DSP1042-SystemVirtualization-1.0.0 and host
> guaranine.danplanet.com is
> > EnabState = 5 EnabDefault = 2 ReqSt = 12
> > ====02_reverse.py Log====
>
> The lack of a log for 02 is troubling.
>
> > HostSystem - 02_hostsystem_to_rasd.py: FAIL
> > Traceback (most recent call last):
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in emit
> >     msg = self.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in format
> >     return fmt.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in format
> >     record.message = record.getMessage()
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in
getMessage
> >     msg = msg % self.args
> > TypeError: not enough arguments for format string
>
  Also passed during my test.

> Looks like a testcase error.
>
> > RASD - 01_verify_rasd_fields.py: FAIL
>
> No log for this one either.
>
> > RASD - 02_enum.py: FAIL
> > Traceback (most recent call last):
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in emit
> >     msg = self.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in format
> >     return fmt.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in format
> >     record.message = record.getMessage()
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in
getMessage
> >     msg = msg % self.args
> > TypeError: not enough arguments for format string
>
> Same as above.
  Also passed during my running test.
>
> > SettingsDefine - 01_forward.py: FAIL
> > SettingsDefine - 02_reverse.py: FAIL
> > SettingsDefine - 03_sds_fwd_errs.py: FAIL
>
> No log.
>
> > SystemDevice - 01_forward.py: FAIL
>
> Log:
>
> > ====01_forward.py Log====
> > Examined test_domain/00:11:22:33:44:55
> > Examined test_domain/mem
> > Examined test_domain/xvdb
> > Examined test_domain/0
>
> > SystemDevice - 03_fwderrs.py: FAIL
> > Traceback (most recent call last):
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in emit
> >     msg = self.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in format
> >     return fmt.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in format
> >     record.message = record.getMessage()
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in
getMessage
> >     msg = msg % self.args
> > TypeError: not all arguments converted during string formatting
>
> This is repeated a bunch of times, but I've snipped them out.
>
> > VSSD - 04_vssd_to_rasd.py: FAIL
> > Traceback (most recent call last):
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in emit
> >     msg = self.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in format
> >     return fmt.format(record)
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in format
> >     record.message = record.getMessage()
> >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in
getMessage
> >     msg = msg % self.args
> > TypeError: not enough arguments for format string
>
> Seems to be a common issue.
>
> > VirtualSystemManagementService - 05_destroysystem_neg.py: FAIL
>
> Log:
>
> > destroy_fail>>nonexistent: Got expected return code 4
> > destroy_fail>>nonexistent: Got expected return code 4
>
> > VirtualSystemMigrationSettingData - 01_enum.py: FAIL
>
> No log.
>
> > VirtualSystemSnapshotServiceCapabilities - 01_enum.py: FAIL
>
> No log.
> [attachment "att9euba.dat" deleted by Guo Lian Yun/China/IBM]
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim at redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-cim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-cim/attachments/20080407/9646f136/attachment.htm>