Relax Testcontainers image pull timeouts

[AlexeyKuznetsov-DD]

What Does This Do

Relax Testcontainers image-pull defaults in the shared test convention:

Setting	Testcontainers 1.21.4 default	Proposed default
TESTCONTAINERS_PULL_TIMEOUT	120 seconds	240 seconds
TESTCONTAINERS_PULL_PAUSE_TIMEOUT	30 seconds	60 seconds

The defaults apply to all Test tasks using this convention, including forked and latest-dependency suites. putIfAbsent preserves explicit environment overrides. Container startup/readiness timeouts are unchanged.

This is an unproven mitigation attempt, not a root-cause fix. The intent is to give temporarily stalled image pulls more time to recover; we hope this reduces failures, but the observed CI stall has not been reproduced locally.

Motivation

CouchbaseClient31V0Test failed during image fetching, before container creation or Couchbase initialization. The test report showed repeated Docker image pull has not made progress in 30s - aborting pull messages, followed by exhaustion of the image-pull retry window. A SQL Server test in the same run failed with the same image-fetch timeout chain, supporting a shared runner/registry issue rather than a Couchbase-specific startup regression.

Precedent: #12723 retries an IOException during Couchbase node renaming after container startup begins. This failure occurs earlier, so that retry cannot address it. That PR changed neither image-pull timeout; this investigation found no evidence that it introduced the reported failure. The evidence also does not establish whether the original node-renaming race is fully resolved.

Also I noticed that OracleContainer very close to default 120s timeout, so better to have more time.

Additional Notes

Concrete failure evidence, with the registry reference omitted:

CouchbaseClient31V0Test > initializationError
ContainerLaunchException: Container startup failed
Caused by: ContainerFetchException: Can't get Docker image
Caused by: ConditionTimeoutException: ... was not fulfilled within 2 minutes.

Docker image pull has not made progress in 30s - aborting pull
Retrying pull for image: ... (83s remaining)
Docker image pull has not made progress in 30s - aborting pull
Retrying pull for image: ... (39s remaining)
Docker image pull has not made progress in 30s - aborting pull
Retrying pull for image: ... (-15s remaining)

The pause timeout is an inactivity watchdog: Docker download/extraction progress updates reset it. When it expires, Testcontainers interrupts that pull and retries internally while its overall retry window allows, before the test fails and Develocity retries the test. The total timeout is a retry window, not a strict wall-clock cap: an active attempt can run beyond it. These settings do not guarantee a fixed number of retries.

The test passed on a Develocity retry. That is consistent with a transient stall, but does not prove that relaxing either timeout fixes it. The registry may have recovered, or Docker may have reused layers downloaded during the failed attempt. Docker daemon/pull-progress evidence is needed to distinguish slow progress from a permanently stuck pull. Longer timeouts also delay reporting genuine pull failures.

Validation: the four shared Couchbase retry unit tests and the Couchbase 3.1/3.2 V0 latest-dependency suites (10 and 12 tests) passed locally with the shared convention. This exercises normal container startup and tracing; it does not reproduce or prove recovery from the CI image-pull stall.

./gradlew :dd-java-agent:instrumentation:couchbase:couchbase-3-common:test \
  :dd-java-agent:instrumentation:couchbase:couchbase-3.1:latestDepTest --tests CouchbaseClient31V0Test \
  :dd-java-agent:instrumentation:couchbase:couchbase-3.2:latestDepTest --tests CouchbaseClient32V0Test

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

[datadog-prod-us1-6]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.35% (+0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 88d725d | Docs | Give us feedback!}

[dd-octo-sts]

🟡 Java Benchmark SLOs — Performance SLO warning (near threshold)

Suite	Status
Startup	🟡 warning

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.78 s	14.67 s	[-0.0%; +1.5%] (no difference)
startup:insecure-bank:tracing:Agent	13.53 s	13.67 s	[-1.9%; -0.1%] (maybe better)
startup:petclinic:appsec:Agent	17.80 s	17.52 s	[+0.7%; +2.5%] (maybe worse)
startup:petclinic:iast:Agent	17.41 s	17.50 s	[-1.2%; +0.2%] (no difference)
startup:petclinic:profiling:Agent	17.36 s	17.15 s	[-0.0%; +2.4%] (no difference)
startup:petclinic:sca:Agent	17.70 s	17.64 s	[-0.5%; +1.2%] (no difference)
startup:petclinic:tracing:Agent	16.50 s	16.69 s	[-2.1%; -0.2%] (maybe better)

Commit: 88d725d2 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-09T17:31:36.090201Z	c8fc514	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-09T17:29:58.452864Z	c8fc514	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c8fc514cbe

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-prod-us1-6]

More details

The longer image-pull defaults preserve inherited environment overrides. Recovery from the reported CI image-pull stall remains unproven.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit c8fc514}

[datadog-prod-us1-6]

More details

The timeout variables are correctly configured in GitLab’s shared test-job template, targeting CI image pulls. Recovery from the reported image-pull stall remains unproven.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 88d725d}

[AlexeyKuznetsov-DD]

/merge -f --reason "No need to run MQ, since it is CI change only, validated in PR"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-09 19:10:59 UTC ℹ️ Start processing command /merge -f --reason "No need to run MQ, since it is CI change only, validated in PR"

---

2026-10-09 19:11:03 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-10-09 19:11:13 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: No need to run MQ, since it is CI change only, validated in PR