test: Relax TempLocationManagerTest concurrent cleanup deadline to 60s

[jbachorik]

What Does This Do

Relaxes the TempLocationManagerTest concurrent cleanup deadline from 30 to 60 seconds.

Motivation

The 30-second deadline assumes an unloaded machine. On busy runners the concurrent cleanup assertions time out, and the test fails intermittently. 60 seconds keeps the test meaningful and removes the intermittent failures.

Additional Notes

Standalone change. Not part of the OTLP profiles stack.

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
• 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

Jira ticket: [PROJ-IDENT]

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

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	13.90 s	13.92 s	[-0.8%; +0.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.92 s	12.94 s	[-0.8%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	17.14 s	16.97 s	[+0.0%; +1.9%] (maybe worse)
startup:petclinic:iast:Agent	17.06 s	16.97 s	[-0.3%; +1.3%] (no difference)
startup:petclinic:profiling:Agent	16.79 s	16.82 s	[-1.1%; +0.7%] (no difference)
startup:petclinic:sca:Agent	17.09 s	16.42 s	[-0.4%; +8.6%] (no difference)
startup:petclinic:tracing:Agent	16.12 s	16.01 s	[-0.4%; +1.8%] (no difference)

Commit: bda22da9 · 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.