boulder: Clean out PGO profiling data between runs - #877
Open
joebonrichie wants to merge 1 commit into
Open
joebonrichie wants to merge 1 commit into
joebonrichie wants to merge 1 commit into
Conversation
Before, stale profiling data would remain present in-between runs causing potentially stale data to affect optimization in the PGO use stage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before, stale profiling data would remain present in-between runs causing potentially stale data to affect optimization in the PGO use stage.
Also taken the opportunity to create a separate pgo_dir function to avoid duplication when formatting the pgo_dir