potiuk commented on pull request #21162:
URL: https://github.com/apache/airflow/pull/21162#issuecomment-1026049782


   > Is it expected that the `Providers` tests in the "Tests: Always API Core 
Other CLI Providers Integration" suite doesn't run for MySQL and MSSQL? I was 
surprised that only Postgres and Sqlite failed.
   
   Yes. That was done as part of stabilizing our flaky CI Tests.
   
   Both MySQL and MSSQL (despite very aggressive optimisation of the 
configuration of the dockerized versions of those) require much more memory to 
run than Postgres and SQLite. That lead to Jobs failing quite often when they 
were run on Public Runners.  That's why they are disabled now for those two 
databases (but only on Public Runners). 
   
   In fact, it is actually even printed there. If you unfold "Determine how to 
run the tests" in those tests you will see this:
   
   
![image](https://user-images.githubusercontent.com/595491/151846256-fff9c662-513b-4f6c-bc0f-34d51c5be215.png)
   
   You will find the logic controlling it here 
https://github.com/apache/airflow/blob/906d710060ebfe893ef3d7cddf00d2c49c7998fa/scripts/ci/testing/ci_run_airflow_testing.sh#L68
   
   Also "all" tests will run in "main" after the change is merged. Those tests 
are run on our 64GB mem self-hosted machines, that have enough CPUS and memory 
to run all the tests always in parallell. So we will see failing main in case 
those "Providers" tests run on MySQL or MsSQL woudl fail (which is highly 
unlikely because Provider tests are not supposed to be "Metadata-DB" dependent. 
Yet we "just in case" always run all tests in main. 
    


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to