-
Notifications
You must be signed in to change notification settings - Fork 16.4k
RDS Instance System Tests #26733
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
RDS Instance System Tests #26733
Conversation
|
|
||
| # This test needs watcher in order to properly mark success/failure | ||
| # when "tearDown" task with trigger rule is part of the DAG | ||
| list(dag.tasks) >> watcher() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This additional list calls is unnecessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed for system tests which have trigger_rule='ALL_DONE' on one of the tasks. Even if either of the first two tasks fail, the third (delete_db_instance) will trigger, and the test will still mark as a pass without the watcher.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird, I thought dag.tasks already returns a (new) list
Lines 1163 to 1165 in 685f523
| @property | |
| def tasks(self) -> list[Operator]: | |
| return list(self.task_dict.values()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My apologies, I misunderstood and thought you were saying the whole line was not needed.
Yeah, interesting. That block is a copy/paste from the AIP-47 specification, and all of the previous system tests do it this way. But it does look like maybe it isn't required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to keep it standardized like all of the others and fix them all later, unless you feel strongly about changing this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a good reason we added it first and possibly it has changed since by modifying "tasks" property to return list. As @ferruzzi wrote - better to keep it consistent and we might want to remove the list as a final refactor.
Follows the template set forward in #24643
Fixed, squashed, and rebased version of #26683 which I can't reopen.