fix(bench): provide explicit Fly build-only config - #1001
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
Included review availability: 1 review is currently available. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour. WalkthroughThe Fly adapter now requires an absolute build configuration path and passes it to ChangesFly build configuration
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The PR adds an explicit, identity-free Fly build-only configuration and makes execution independent of the caller’s working directory while preserving the existing build behavior; validation checks pass, and no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description provides a clear summary, root cause, implementation details, validation results, issue reference, and resource impact. It does not use every template heading or checklist item, but the core required information is complete. Full details: Docstring CoverageExplanation Docstring coverage is 11.11% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 4 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
--appRoot cause evidence
After PR #1000, app readiness converged in the authorized post-fix attempt, but
flyctl deploy --build-onlystill returned typedbuild_failedbefore image resolution. The repository had nofly.tomland the executor supplied no explicit--config, while Fly deploy consumes app configuration from that path.Validation
make -C benchmarks fly-adapter-static— 29 passedmake -C benchmarks smoke-python— smoke passed; 83 passedpython3 scripts/ci/test-fly-filesystem-safety-contract.py— 2 passedgit diff --check— passedIssue
Relates to issue 958. It remains open; a merged-executor tiny rerun with qualified evidence and independent teardown remains the completion gate.
No Fly resources were created by this change.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit
New Features
Bug Fixes