Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving from flytepropeller - Adding flags for ignore-retry-cause and default-max-attempts #4153

Merged

Conversation

eapolinario
Copy link
Contributor

TL;DR

Adding flags to simplify retry behavior. ignore-retry-cause means that system and user failures are treated the same and default-max-attempts sets a default number of retries for tasks.

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Complete description

^^^

Tracking Issue

NA

Follow-up issue

NA

hamersaw and others added 14 commits July 26, 2023 10:13
Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Daniel Rammer <[email protected]>
* Cleanup retry behavior

Signed-off-by: Dennis Keck <[email protected]>

* Fix interruptible retry threshold for odl behavior

Signed-off-by: Dennis Keck <[email protected]>

* Add tests for BuildNodeExecutionContext

Signed-off-by: Dennis Keck <[email protected]>

* Fix IsElgibileForRetries Tests

Signed-off-by: Dennis Keck <[email protected]>

---------

Signed-off-by: Dennis Keck <[email protected]>
Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Daniel Rammer <[email protected]>
Signed-off-by: Eduardo Apolinario <[email protected]>
@codecov
Copy link

codecov bot commented Oct 3, 2023

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (4ee73f5) 59.44% compared to head (89eaa65) 59.32%.

❗ Current head 89eaa65 differs from pull request most recent head d767dc0. Consider uploading reports for the commit d767dc0 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4153      +/-   ##
==========================================
- Coverage   59.44%   59.32%   -0.13%     
==========================================
  Files         637      550      -87     
  Lines       54262    39710   -14552     
==========================================
- Hits        32254    23556    -8698     
+ Misses      19467    13834    -5633     
+ Partials     2541     2320     -221     
Flag Coverage Δ
unittests ?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
...go/tasks/plugins/array/k8s/subtask_exec_context.go 83.18% <100.00%> (+1.36%) ⬆️
...tepropeller/pkg/compiler/transformers/k8s/utils.go 87.01% <100.00%> (+0.27%) ⬆️
flytepropeller/pkg/controller/config/config.go 0.00% <ø> (ø)
...ytepropeller/pkg/controller/config/config_flags.go 75.94% <100.00%> (+2.53%) ⬆️
...ytepropeller/pkg/controller/nodes/array/handler.go 70.37% <100.00%> (+1.01%) ⬆️
flytepropeller/pkg/controller/nodes/executor.go 61.61% <100.00%> (+1.21%) ⬆️
...ller/pkg/controller/nodes/task/taskexec_context.go 80.13% <100.00%> (+1.12%) ⬆️
...ropeller/pkg/controller/nodes/node_exec_context.go 84.74% <81.25%> (+2.20%) ⬆️

... and 567 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor Author

@eapolinario eapolinario left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I can't approve a PR I opened. 😂

@hamersaw hamersaw merged commit a903dc0 into master Oct 6, 2023
35 of 36 checks passed
@hamersaw hamersaw deleted the monorepo-move/flytepropeller/feature/simplify-retries branch October 6, 2023 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants