Internal - delete unused benchmark.yml workflow#494
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the standalone GitHub Actions workflow used to run benchmarks (Benchmark), with the intent to rely on the benchmark job that exists in the Push workflow instead.
Changes:
- Deleted the
.github/workflows/benchmark.ymlworkflow definition.
Comments suppressed due to low confidence (1)
.github/workflows/benchmark.yml:1
- Deleting this workflow removes features that the PR description says are already replaced: this file provided a manually-triggered (workflow_dispatch) benchmark run with inputs (agent-type/container-logs) and persisted results by committing to the
benchmark-resultsbranch. The current.github/workflows/push.ymlbenchmarkjob (around lines 423-458) only runs./gradlew testand uploads artifacts, and there is still documentation pointing users to run theBenchmarkworkflow and to fetch results frombenchmark-results(seebenchmark/README.md:8-30). Either update the push workflow/docs to match the previous behavior, or clarify in the PR description that the result-publishing/manual-run functionality is being intentionally removed.
jerrytfleung
approved these changes
May 21, 2026
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
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.
Summary
Fix feature test failures caused by the upstream
opentelemetry-agent-for-testingoverriding theotel.propagatorsproperty, remove unused benchmark workflow, and fix minor code style issues.Details
Fix propagator override in test agent
The upstream
opentelemetry-agent-for-testingjar contains anAutoConfigurationCustomizerProviderthat overridesotel.propagatorsset bySolarwindsPropertiesSupplier. This causedSolarwindsContextPropagatorto be absent from the composite propagator during tests, resulting in 3 test failures (context propagation and trigger trace tests).Since
DefaultConfigPropertiesresolution order is systemProperties > environmentVariables > defaultProperties, explicitly setting-Dotel.propagators=tracecontext,baggage,solarwindsas a JVM system property in the feature-tests module guarantees the SolarWinds propagator is always registered regardless of supplier ordering.Remove unused benchmark workflow
The
benchmark.ymlGitHub Actions workflow was unused and removed.Code style fixes
W3C→W3c)ignore→ignored)Test services data