bart02 opened a new issue, #48451:
URL: https://github.com/apache/airflow/issues/48451
### Apache Airflow version
2.10.5
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
I have created a DAG where setup task depends on branching operator
(`do_start_inference`).
When I start it and branching operator tells that `get_job_id` should be
started, and `start_serving` should be skipped, get_job_id task also skips even
if it has ONE_SUCCESS trigger rule.
This behaviour is only happens when using setup / teardown. If I delete
`setups=start_serving` from `as_teardown` everything is OK.
Dependencies:
```
benchmarks = [mera, arena_gen, arena_hard, arena_inhouse_gen,
arena_inhouse_proxy_prod_sample, mbpp_ru, mmlu_pro, math_eval, alpaca_eval,
mt_bench]
do_start_inference >> [get_job_id, start_serving]
start_serving >> wait_until_started >> get_job_id >> benchmarks >>
kill_serving.as_teardown(setups=start_serving)
select_benchmarks_from_params() >> benchmarks >> upload_to_db
```
<img width="1029" alt="Image"
src="https://github.com/user-attachments/assets/50e1105c-8226-4573-8945-39c5621e16a1";
/>
### What you think should happen instead?
`get_job_id` shouldn't be skipped when using setup / teardown
### How to reproduce
Create a DAG where setup task depends on branching operator, and run this
DAG so that the branching operator goes down the branch without a setup.
### Operating System
MacOS
### Versions of Apache Airflow Providers
_No response_
### Deployment
Virtualenv installation
### Deployment details
standalone
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
