Increase window to retry a failed job in MQ

[bric3]

What Does This Do

Increased the timeout for rerunning failed jobs in MQ.

Motivation

Allow contributors to avoid re-adding a PR to the merge queue.

Additional Notes

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

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	14.07 s	14.02 s	[-0.4%; +1.2%] (no difference)
startup:insecure-bank:tracing:Agent	12.92 s	13.07 s	[-1.9%; -0.4%] (maybe better)
startup:petclinic:appsec:Agent	17.19 s	17.14 s	[-0.6%; +1.1%] (no difference)
startup:petclinic:iast:Agent	16.98 s	17.16 s	[-1.8%; -0.3%] (maybe better)
startup:petclinic:profiling:Agent	16.56 s	16.93 s	[-3.4%; -0.9%] (maybe better)
startup:petclinic:sca:Agent	17.15 s	16.91 s	[+0.4%; +2.4%] (maybe worse)
startup:petclinic:tracing:Agent	16.15 s	16.26 s	[-1.5%; +0.1%] (no difference)

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