PGO: Remove profraw files from device after pulling to local The generated profraw files on the device are named like child_pool-[0-3].profraw. Typically, 1 to 4 such files are randomly generated per run. The script pulls the generated profraw files from the device once per benchmark, but the profraw files on the device are not removed after being pulled. This means the next benchmark run has a high possibility of pulling duplicate profraw files that were generated in the previous run. This change removes the profraw files from the device once they are pulled to the local machine. BUG=411331786 TEST=Run generate_profile.py with a public benchmark, and check that the pulled profraw files have no duplicates. Change-Id: I47bb4464937ae6a2e83b67558777d9f360eb3d6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6467347 Reviewed-by: Wenbin Zhang <wenbinzhang@google.com> Reviewed-by: John Chen <johnchen@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Auto-Submit: Darren Wu <darrenwu@chromium.org> Cr-Commit-Position: refs/heads/main@{#1450570}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.