[v2-10-test] Fix k8s flaky test_integration_run_dag_with_scheduler_failure#49101
Merged
jason810496 merged 3 commits intoapache:v2-10-testfrom Apr 22, 2025
Conversation
d52e2f5 to
533107c
Compare
533107c to
4679000
Compare
Member
Author
4679000 to
001308a
Compare
- Note that LocalExecutor use statefulset for scheduler instead of deployment
001308a to
ff7dc38
Compare
jscheffl
approved these changes
Apr 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
While fixing CI on the
v2-10-testbranch, I noticed that some Kubernetes tests are flaky.For example: https://github.com/apache/airflow/actions/runs/14176933252/job/39716299877
We should port #46502 (Fix flaky Kubernetes test:
test_integration_run_dag_with_scheduler_failure) to thev2-10-testbranch.