Clean up remaining DB-dependent tests from OpenSearch provider #52235
Conversation
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
aa33924 to
3d38483
Compare
|
Sorry - opensearch already done :) |
72 tasks
|
Ah .. OK then :) sorry. |
|
BTW. We will do a separate thing about getting rid of potentially "all" db_tests as next step - this might involve much heavier refaactorings - for example splitting out executors and providers that |
potiuk
approved these changes
Jun 25, 2025
27c439a to
7152700
Compare
|
Once the commits are cleaned up and ready, I’ll request a review. |
7152700 to
d918c3f
Compare
…s in test_os_task_handler with @pytest.mark.db_test
d918c3f to
e1634ba
Compare
kyungjunleeme
commented
Jun 26, 2025
…ommit-config.yaml
|
@potiuk hello, Could you review my pr? |
potiuk
approved these changes
Jun 26, 2025
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.
Part of #52020
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.--- related with #52213