phase a/fixups pipeline smoke#45
Conversation
aksOps
commented
Apr 17, 2026
aksOps
commented
- chore(baseline): scaffold baseline dirs and gitignore
- chore(baseline): add seed-repo fetch script with pinned commits
- chore(baseline): add Maven verify + JaCoCo capture script
- chore(baseline): add flaky-test scan (N repeated runs)
- chore(baseline): add SpotBugs baseline capture
- chore(baseline): add dependency-tree + license snapshot capture
- chore(baseline): add frontend audit (npm audit + Vite + Playwright)
- chore(baseline): add index/enrich/serve-smoke pipeline capture
- chore(baseline): run pipeline on realworld-express
- chore(baseline): add OWASP dependency-check baseline capture (NVD sync needs retry)
- chore(baseline): add consolidator and publish first BASELINE.md
- fix(baseline): probe /api/stats for serve-smoke readiness instead of /actuator/health
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 5 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…/actuator/health
The original baseline captured health=fail on both seed repos. Initial
hypothesis was that the 8s sleep was too short for Spring Boot + Neo4j
cold start. Live probing showed otherwise:
- /actuator/health returns HTTP 503 with body
{"groups":["liveness","readiness"],"status":"OUT_OF_SERVICE"}
at ALL times, even after the graph is fully loaded.
- /api/stats returns HTTP 200 within ~10-11s on both seeds, populated
with real graph data (691/1836 nodes/edges for petclinic, 224/297
for realworld-express).
The real bug is in GraphHealthIndicator, which flags the app as
OUT_OF_SERVICE despite a loaded graph. Filed as a separate known gap
for a future fix; out of scope for getting the baseline unblocked.
Changes to scripts/baseline/run-pipeline.sh:
- Poll /api/stats (30 x 2s = 60s budget) for readiness. /api/stats is
the public REST surface and returns iff the graph is loaded.
- Capture /actuator/health HTTP code + body as a diagnostic; do not
gate readiness on it.
- Truncate timings.txt at the start of each run so re-runs don't
accumulate stale entries.
- Summary JSON now reports stats_ok (real readiness) and health_raw
(diagnostic body) rather than health_ok.
BASELINE.md:
- Marks pipeline serve-smoke gap as RESOLVED with real timings + stats
for both seeds.
- Adds a new known gap for the GraphHealthIndicator 503 issue.
aksOps
force-pushed
the
phase-a/fixups-pipeline-smoke
branch
from
f23e05e to
af46fca
Compare
|
1 participant
