Open Bug 1372862 Opened 2 years ago Updated 2 years ago

create easier method to parse xperf filenames

Categories

(Testing :: Talos, enhancement)

enhancement
Not set

Tracking

(Not tracked)

People

(Reporter: jmaher, Unassigned)

References

Details

Attachments

(1 file)

when bug 1372857 is resolved, there are still the next steps to figure out.

specifically:
I see solving #2/#3/#4 by writing a script which will live in tree an you can run it sort of like this:
python testing/talos/talos/xtalos/xperf_differences.py --baseBranch <branch> --baseRevision <rev> --newBranch <branch> --newRevision <rev> --stage <startup|normal> --thread <main|nonmain>

this would somehow figure out where the etl_output.csv file is for each revision and download them, then parse them and summarize the data.

Since I am doing this for bug 1371649, I will upload the script I have, ideally we can make it more formal.
Attached file parse_xperf.py
example patch assuming downloaded two etl_output.csv (download as .gz and gunzip them) files and places as good_output.csv and bad_output.csv in the same directory.
Depends on: 1372857
You need to log in before you can comment on or make changes to this bug.