Repository navigation
Make CI curl calls fail on HTTP errors and retry - #12911
cbeauchesne wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Debugger benchmarksParameters
See matching parameters
SummaryFound 5 performance improvements and 0 performance regressions! Performance is the same for 4 metrics, 6 unstable metrics.
See unchanged results
Request duration reports for reportsgantt
title reports - request duration [CI 0.99] : candidate=None, baseline=None
dateFormat X
axisFormat %s
section baseline
noprobe (363.799 µs) : 341, 387
. : milestone, 364,
basic (346.617 µs) : 341, 352
. : milestone, 347,
loop (8.93 ms) : 8743, 9118
. : milestone, 8930,
section candidate
noprobe (394.926 µs) : 354, 436
. : milestone, 395,
basic (343.213 µs) : 340, 347
. : milestone, 343,
loop (7.591 ms) : 7583, 7599
. : milestone, 7591,
|
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6cbff64af9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
More details
HTTP download failures now stop SDKMAN installation, while the test-agent checks preserve valid 404 handling. The completed static review found no reportable regressions.
🤖 Bits Code Review · Commit 6cbff64
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What Does This Do
Every
curlrun in CI on PRs andmasterpushes now fails on HTTP errors (--fail) and retries transient failures. A "CI scripts" rule inAGENTS.mdmakes new CI code follow the same pattern.Motivation
Without retries, network blips break jobs. Without
--fail, a 4xx/5xx exits 0: the exploration-tests image rancurl -s https://get.sdkman.io | bash, so a failed download silently installed nothing.Additional Notes
check_test_agent_results.shkeeps its explicit HTTP status checks (a 404 is a valid answer there) and only gains retries.mvnw, and the tag/release-only jobs.🤖 Generated with Claude Code