Optimize test execution time after refactors #44089
Merged
+12
−6
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
After refactor of running providers tests and after some recent changes we need to re-sort the order of test type execution and separate out standards provider. Ths "standard" provider has slow Venv tests and it is now the slowest provider when it comes to test suite. Similarly API test type has many more tests now and it is pretty slow. Both should be started earlier in order to make use of the parallelism we have (long running tests should go first to avoid them to stay as last ones and utilise only one processor while doing so. This PR separates standard provider and moves both standard provider and API to the top of the list used for sorting, similarly google and amazon are put higher on the list
There was a problem hiding this comment.
Copilot reviewed 3 out of 3 changed files in this pull request and generated no suggestions.
potiuk
requested review from
ephraimbuddy,
pierrejeambrun,
rawwar,
romsharon98,
vatsrahul1001 and
eladkal
gopidesupavan
approved these changes
Nov 16, 2024
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.
After refactor of running providers tests and after some recent changes we need to re-sort the order of test type execution and separate out standards provider.
Ths "standard" provider has slow Venv tests and it is now the slowest provider when it comes to test suite. Similarly API test type has many more tests now and it is pretty slow. Both should be started earlier in order to make use of the parallelism we have (long running tests should go first to avoid them to stay as last ones and utilise only one processor while doing so.
This PR separates standard provider and moves both standard provider and API to the top of the list used for sorting, similarly google and amazon are put higher on the list
^ 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.