open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Investigate reducing JMX metrics library test runtime
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
:instrumentation:jmx-metrics:library:test can exceed the 15-minute timeout on cold CI runners while Testcontainers pulls and starts its images.
Describe the solution you'd like
Reduce cold-start overhead by pre-pulling or caching images, or shard the container-backed tests, so the task stays below 15 minutes.
Describe alternatives you've considered
#19940 raises this task's timeout to 30 minutes as a short-term workaround.
Additional context
In the observed failure, 14 JMX image pulls reported 146 seconds of download time. The final Kafka image completed 25 seconds before the task timed out.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with :instrumentation:jmx-metrics:library:test and inspect how its Testcontainers-backed tests pull and start the JMX images, including the final Kafka image. Measure cold CI runtime and evaluate the proposed caching, pre-pulling, or sharding options; done means the task reliably stays below 15 minutes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100