Re: kvm-unit-testing: Test results parsing vs tap13

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 23/01/20 14:23, Naresh Kamboju wrote:
> 
> We (Linaro) are validating LTS branches and mainline and linux-next by
> using kvm-unit-test repo and reporting test results for stable rc
> reviews. kvm-unit-tests are running on x86_64 and arm64 architectures.
> 
> I need your opinion on running test with available options.
> 
> The current test definitions run_tests.sh running with option -v.
> 
>  ./run_tests.sh -v
> 
> If I run with option -t (---tap13)  47355 results showed on the console.
> With TAP13 it is a huge number of results compared with option -v -a
> the 57 test case results.

The TAP option is simply more detailed than the default, which
aggregates all the tests from a single executable in a single line.  You
can see that in the non-TAP options output, which is

PASS apic-split (53 tests)
PASS ioapic-split (19 tests)

etc.

If you sum the results (53+19+...) the number you get should be very
close to 47355.

Thanks,

Paolo




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux