Bug 1363 - DTS improve statistics.txt
Summary: DTS improve statistics.txt
Status: UNCONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: DTS (show other bugs)
Version: unspecified
Hardware: All All
: High critical
Target Milestone: ---
Assignee: Juraj Linkeš
URL:
Depends on:
Blocks:
 
Reported: 2024-01-10 13:23 CET by Juraj Linkeš
Modified: 2024-02-15 16:25 CET (History)
2 users (show)



Attachments

Description Juraj Linkeš 2024-01-10 13:23:25 CET
The current statistics are so simple to the point of possibly being inaccurate.

The information comes partially from one build target (like DPDK version) and then from all executions (such as the number of tests run).

Let’s include basic information about each build target (version, pass/fail/block/skip numbers) and then a summary at the end.
Comment 1 Juraj Linkeš 2024-01-10 13:24:01 CET
We could refine some of the SutNode setters when doing this:

add setters for SutNode.remote_dpdk_build_dir (so that we don't call the methods multiple times) and SutNode.dpdk_version (as we're setting self._dpdk_version elsewhere)?
also for SutNode.get_build_target_info


we should probably combine SutNode.dpdk_version and SutNode.compiler_version with SutNode.get_build_target_info
Comment 2 Patrick Robb 2024-02-15 16:25:58 CET
(First pass draft idea)

Should break down statistics by:

-cumulative pass/fails

-per build target:
    -per testsuite
        -per testcase(?)

Also should list some dpdk artifact/environment info:

YAML/JSON can be used.

Note You need to log in before you can comment on or make changes to this bug.