On 09/20/2012 06:56 AM, Prem Karat wrote:
Am trying to run a test from libvirt (virsh_cpu_stats) and I see that when I set a pdb trace using pdb.set_trace() in the code, it enters/invokes the debugger but no output is shown from the debugger. But I guess it can step through or goto next instruction. PDB also responds to 'c' command and when 'c' command is given it goes through until it finds pdb.set_trace() again. Here is the problem. [root@phx3 virt]# ./run -t libvirt/ DEBUG LOG: /home/autotest/client/tests/virt/logs/run-2012-09-21-14.57.30/debug.log TESTS: 20 libvirt.raw.virtio_blk.smp2.virtio_net.Fedora.17.64.virsh_cpu_stats.libvirton.expected_options.expected_option_none:n s s p vm_name s s n c FAIL (21.76 s) libvirt.raw.virtio_blk.smp2.virtio_net.Fedora.17.64.virsh_cpu_stats.libvirton.expected_options.expected_option_start:c As you can see above nothing is getting displayed. Same problem is seen when I use verbose output. Did I miss something?
In order to get the clean output with the run script, I had to do some tricks with regards to stdout/stderr. I actually expected things to work with --verbose, but...
Well, in the meantime you might run the tests under autotest rather than the run script?
../../autotest-local libvirt/control --verbose I'll take a look at this as soon as possible. Lucas _______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
