-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
[QUARANTINE] The test_scheduler_verify_pool_full test is quarantined #17224
Labels
kind:bug
This is a clearly a bug
Quarantine
Issues that are occasionally failing and are quarantined
Comments
potiuk
added
kind:bug
This is a clearly a bug
Quarantine
Issues that are occasionally failing and are quarantined
labels
Jul 26, 2021
potiuk
added a commit
to potiuk/airflow
that referenced
this issue
Jul 26, 2021
The test fails occasionally as noted in apache#17224
potiuk
added a commit
that referenced
this issue
Jul 26, 2021
The test fails occasionally as noted in #17224
potiuk
added a commit
to potiuk/airflow
that referenced
this issue
Dec 11, 2021
The scheduler job tests were pretty flaky and some of them were quarantined already (especially the query count). This PR improves the stability in the following ways: * clean the database between tests for TestSchedulerJob to avoid side effects * forces UTC timezone in tests where date missed timezone specs * updates number of queries expected in the query count tests * stabilizes the sequence of retrieval of tasks in case tests depended on it * adds more stack trace levels (5) to compare where extra methods were called. * increase number of scheduler runs where it was needed * add session.flush() where it was missing * add requirement to have serialized dags ready when needed * increase dagruns number to process where we could have some "too slow" tests comparing to fast processing of dag runs. Hopefully: * Fixes: apache#18777 * Fixes: apache#17291 * Fixes: apache#17224 * Fixes: apache#15255 * Fixes: apache#15085
potiuk
added a commit
that referenced
this issue
Dec 13, 2021
* Restore stability and unquarantine all test_scheduler_job tests The scheduler job tests were pretty flaky and some of them were quarantined already (especially the query count). This PR improves the stability in the following ways: * clean the database between tests for TestSchedulerJob to avoid side effects * forces UTC timezone in tests where date missed timezone specs * updates number of queries expected in the query count tests * stabilizes the sequence of retrieval of tasks in case tests depended on it * adds more stack trace levels (5) to compare where extra methods were called. * increase number of scheduler runs where it was needed * add session.flush() where it was missing * add requirement to have serialized dags ready when needed * increase dagruns number to process where we could have some "too slow" tests comparing to fast processing of dag runs. Hopefully: * Fixes: #18777 * Fixes: #17291 * Fixes: #17224 * Fixes: #15255 * Fixes: #15085 * Update tests/jobs/test_scheduler_job.py Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
potiuk
added a commit
that referenced
this issue
Jan 22, 2022
* Restore stability and unquarantine all test_scheduler_job tests The scheduler job tests were pretty flaky and some of them were quarantined already (especially the query count). This PR improves the stability in the following ways: * clean the database between tests for TestSchedulerJob to avoid side effects * forces UTC timezone in tests where date missed timezone specs * updates number of queries expected in the query count tests * stabilizes the sequence of retrieval of tasks in case tests depended on it * adds more stack trace levels (5) to compare where extra methods were called. * increase number of scheduler runs where it was needed * add session.flush() where it was missing * add requirement to have serialized dags ready when needed * increase dagruns number to process where we could have some "too slow" tests comparing to fast processing of dag runs. Hopefully: * Fixes: #18777 * Fixes: #17291 * Fixes: #17224 * Fixes: #15255 * Fixes: #15085 * Update tests/jobs/test_scheduler_job.py Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> (cherry picked from commit 9b277db)
jedcunningham
pushed a commit
that referenced
this issue
Jan 27, 2022
* Restore stability and unquarantine all test_scheduler_job tests The scheduler job tests were pretty flaky and some of them were quarantined already (especially the query count). This PR improves the stability in the following ways: * clean the database between tests for TestSchedulerJob to avoid side effects * forces UTC timezone in tests where date missed timezone specs * updates number of queries expected in the query count tests * stabilizes the sequence of retrieval of tasks in case tests depended on it * adds more stack trace levels (5) to compare where extra methods were called. * increase number of scheduler runs where it was needed * add session.flush() where it was missing * add requirement to have serialized dags ready when needed * increase dagruns number to process where we could have some "too slow" tests comparing to fast processing of dag runs. Hopefully: * Fixes: #18777 * Fixes: #17291 * Fixes: #17224 * Fixes: #15255 * Fixes: #15085 * Update tests/jobs/test_scheduler_job.py Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> (cherry picked from commit 9b277db)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind:bug
This is a clearly a bug
Quarantine
Issues that are occasionally failing and are quarantined
The test fails occasionally with the below stacktrace, so I am marking this as Quarantined.
The text was updated successfully, but these errors were encountered: