Another attempt to stabilize (and limit) integration tests #39913
Conversation
This file contains 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
potiuk
force-pushed
the
stabilize-and-limit-integration-tests
branch
3 times, most recently
from
fb84fd8 to
8582dd5
Compare
There is no particular reason we should run the integration tests for both Postgres and mysql - and Postgres ones seem to be much more stable in general, so we only limit the tests to be run the tests for Postgres. Also - since the tests (especially mssql) seem to be flaky, we re-run them once if they fail
potiuk
force-pushed
the
stabilize-and-limit-integration-tests
branch
from
8582dd5 to
c5fe417
Compare
jscheffl
approved these changes
May 29, 2024
fdemiane
pushed a commit
to fdemiane/airflow
that referenced
this pull request
Jun 6, 2024
) There is no particular reason we should run the integration tests for both Postgres and mysql - and Postgres ones seem to be much more stable in general, so we only limit the tests to be run the tests for Postgres. Also - since the tests (especially mssql) seem to be flaky, we re-run them once if they fail
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
) There is no particular reason we should run the integration tests for both Postgres and mysql - and Postgres ones seem to be much more stable in general, so we only limit the tests to be run the tests for Postgres. Also - since the tests (especially mssql) seem to be flaky, we re-run them once if they fail
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.
There is no particular reason we should run the integration tests for both Postgres and mysql - and Postgres ones seem to be much more stable in general, so we only limit the tests to be run the tests for Postgres.
Also - since the tests (especially mssql) seem to be flaky, we re-run them once if they fail.
^ 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 newsfragments.