fournos: set a 24h timeout for the task completion - #102
Conversation
|
Warning Review limit reached
Next review available in: 24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughPipelineRun generation now includes configurable pipeline, task, and finally timeout values. The settings model supplies defaults and descriptions for the three duration parameters. ChangesPipeline timeout configuration
Estimated code review effort: 2 (Simple) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/test deploy-fournos-wip |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@fournos/settings.py`:
- Around line 29-31: Update the description for the pipeline_tasks_timeout Field
to state that it represents the cumulative timeout across non-finally tasks in
PipelineRun, rather than the default timeout for each individual task. Preserve
the existing default value and examples.
- Around line 25-36: Add settings-level validation for pipeline_timeout,
pipeline_tasks_timeout, and pipeline_finally_timeout using the existing settings
validation mechanism, rejecting malformed Go-duration strings and ensuring
pipeline_timeout is at least the combined tasks and finally timeouts. Add tests
covering invalid formats and invalid cross-field combinations, while preserving
valid duration values.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 963fd724-6450-41bc-98fa-067047a4d2bd
📒 Files selected for processing (2)
fournos/core/tekton.pyfournos/settings.py
|
/test deploy-fournos-wip |
|
/test deploy-fournos-wip |
test launched from Forge passed ✅ |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: albertoperdomo2 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
PipelineRun default is 1h:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift-psap_forge/129/pull-ci-openshift-psap-forge-main-fournos/2077705564653096960/artifacts/fournos/fournos/artifacts/001__submit_and_wait/artifacts/pipelinerun.yaml
we'll make that configurable from the fjob later
Summary by CodeRabbit
25h0m0sand90m.