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

[Bug] [Workflow] Fix workflow failure strategy bug #11793

Closed
wants to merge 3 commits into from

Conversation

EricGao888
Copy link
Member

@EricGao888 EricGao888 commented Sep 6, 2022

Purpose of the pull request

Brief change log

Verify this pull request

  • Verified by unit tests and manual tests.

@EricGao888 EricGao888 marked this pull request as ready for review September 6, 2022 05:36
SbloodyS
SbloodyS previously approved these changes Sep 6, 2022
Copy link
Member

@SbloodyS SbloodyS left a comment

Choose a reason for hiding this comment

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

LGTM

@SbloodyS SbloodyS added the bug Something isn't working label Sep 6, 2022
@SbloodyS SbloodyS added this to the 3.0.1 milestone Sep 6, 2022
@codecov-commenter
Copy link

codecov-commenter commented Sep 6, 2022

Codecov Report

Merging #11793 (69bd990) into dev (4283cfd) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev   #11793      +/-   ##
============================================
- Coverage     39.60%   39.58%   -0.02%     
  Complexity     4693     4693              
============================================
  Files          1014     1014              
  Lines         37952    37960       +8     
  Branches       4243     4245       +2     
============================================
- Hits          15030    15027       -3     
- Misses        21315    21326      +11     
  Partials       1607     1607              
Impacted Files Coverage Δ
.../server/master/runner/WorkflowExecuteRunnable.java 7.96% <0.00%> (-0.01%) ⬇️
...erver/master/processor/queue/TaskEventService.java 75.00% <0.00%> (-5.36%) ⬇️
...che/dolphinscheduler/api/python/PythonGateway.java 17.22% <0.00%> (-0.60%) ⬇️
...ler/server/worker/processor/TaskKillProcessor.java 0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

stalary
stalary previously approved these changes Sep 6, 2022
Copy link
Contributor

@stalary stalary left a comment

Choose a reason for hiding this comment

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

LGTM

@EricGao888 EricGao888 dismissed stale reviews from stalary and SbloodyS via cf94b78 September 6, 2022 08:33
@caishunfeng
Copy link
Contributor

I found the UT case WorkflowExecuteRunnableTest.testCheckSerialProcess, can you add a UT case for it?

@EricGao888
Copy link
Member Author

I found the UT case WorkflowExecuteRunnableTest.testCheckSerialProcess, can you add a UT case for it?

@caishunfeng Of course. I will take a look. Thanks for the reminder : )

ruanwenjun
ruanwenjun previously approved these changes Sep 6, 2022
Copy link
Member

@ruanwenjun ruanwenjun left a comment

Choose a reason for hiding this comment

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

LGTM, it will be better if you can add UT.

@EricGao888
Copy link
Member Author

LGTM, it will be better if you can add UT.

Sure, I'm working on it.

…d unit tests for different workflow failure strategies and depend results
@EricGao888
Copy link
Member Author

EricGao888 commented Sep 6, 2022

Refactored some code for better readability and testability. Related unit tests added : ) PTAL @ruanwenjun @caishunfeng @SbloodyS @stalary

@sonarqubecloud
Copy link

sonarqubecloud bot commented Sep 6, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

59.3% 59.3% Coverage
0.0% 0.0% Duplication

Copy link
Member

@SbloodyS SbloodyS left a comment

Choose a reason for hiding this comment

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

+1

Copy link
Contributor

@caishunfeng caishunfeng left a comment

Choose a reason for hiding this comment

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

LGTM 👍

Copy link
Contributor

@lenboo lenboo left a comment

Choose a reason for hiding this comment

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

According to the docs about this feature, I think there are disagreements.

@EricGao888
Copy link
Member Author

According to the docs about this feature, I think there are disagreements.

@lenboo May I ask whether the continue strategy was designed only for parallel execution, or there is an incorrect description in docs? If the latter, I will fix the docs. If the former, we need further discussion. However, IMHO, I think continue strategy should not only work for parallel. Sometimes we need clean up tasks. As described in issue.

image

@EricGao888 EricGao888 requested review from lenboo and removed request for stalary September 7, 2022 03:31
@EricGao888 EricGao888 added the discussion discussion label Sep 7, 2022
@lenboo
Copy link
Contributor

lenboo commented Sep 7, 2022

According to the docs about this feature, I think there are disagreements.

@lenboo May I ask whether the continue strategy was designed only for parallel execution, or there is an incorrect description in docs? If the latter, I will fix the docs. If the former, we need further discussion. However, IMHO, I think continue strategy should not only work for parallel. Sometimes we need clean up tasks. As described in issue.

image

  • Yes, the continue strategy was designed only for parallel tasks.
  • I can understand the scenario you mentioned. Indeed, we need solution to this scenario in another discussion.

@EricGao888
Copy link
Member Author

According to the docs about this feature, I think there are disagreements.

@lenboo May I ask whether the continue strategy was designed only for parallel execution, or there is an incorrect description in docs? If the latter, I will fix the docs. If the former, we need further discussion. However, IMHO, I think continue strategy should not only work for parallel. Sometimes we need clean up tasks. As described in issue.
image

  • Yes, the continue strategy was designed only for parallel tasks.
  • I can understand the scenario you mentioned. Indeed, we need solution to this scenario in another discussion.

@lenboo Thanks for the reply. I've add the topic to community bi-weekly conference topic list, looking forward to the discussion tonight : )

@EricGao888 EricGao888 added improvement make more easy to user or prompt friendly and removed bug Something isn't working labels Sep 9, 2022
@EricGao888 EricGao888 removed this from the 3.0.1 milestone Sep 9, 2022
@EricGao888
Copy link
Member Author

I'm closing it temporarily. Will submit a design later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend discussion discussion don't merge improvement make more easy to user or prompt friendly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] [Workflow] Workflow failure strategy does not work as expected
7 participants