[PROF-9370] Remove separate configuration for benchmarking GC profiling #3571
Conversation
This file contains 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
**What does this PR do?** This PR removes the benchmarking configuration for testing GC profiling. This is because in #3558 GC profiling was enabled by default and so the `only-profiling` configuration now includes GC profiling (and thus we don't need a separate one). **Motivation:** Remove benchmarking configurations that no longer make sense to have. **Additional Notes:** N/A **How to test the change?** Validate this configuration is no longer tested.
AlexJF
approved these changes
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
This PR removes the benchmarking configuration for testing GC profiling.
This is because in #3558 GC profiling was enabled by default and so the
only-profilingconfiguration now includes GC profiling (and thus we don't need a separate one).Motivation:
Remove benchmarking configurations that no longer make sense to have.
Additional Notes:
N/A
How to test the change?
Validate this configuration is no longer tested.
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance.