You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For LTM runs, create a top level results.xml file which combines the per-config results.xml files. Upload this separately form the results.tar.gz file similarly to how we handle the summary file. Then, convert results processing scripts to download just this XML file and use it for processing.
The text was updated successfully, but these errors were encountered:
There is already a file I use for post processing results: ./test-appliance/files/usr/lib/python3/dist-packages/get_stats.py
This stores the results in a condensed XML file.
Instead of an entry for each time a test runs
(ex.
generic/001 -> pass
generic/001 -> pass
generic/002 -> pass
generic/002 -> pass
...)
it instead creates a stats version
(ex.
generic/001 -> skips=0, fail=0, error=0, total=2
generic/002 -> skips=0, fail=0, error=0, total=2
...
)
My other post-processing scripts (merge_stats.py, diff_stats.py) operate on this format XML file to merging results form same kernel or compare results across different kernels. get_stats.py walks through each results directory to find the results similarly to what generate_report does. Perhaps we could combine the two and generate/upload this as the separate XML results file.
The XML file already has creates sections to distinguish between configs <config=XX/YY>.
For LTM runs, create a top level results.xml file which combines the per-config results.xml files. Upload this separately form the results.tar.gz file similarly to how we handle the summary file. Then, convert results processing scripts to download just this XML file and use it for processing.
The text was updated successfully, but these errors were encountered: