potiuk opened a new pull request #10768:
URL: https://github.com/apache/airflow/pull/10768


   We've observed the tests for last couple of weeks and it seems
   most of the tests marked with "quarantine" marker are succeeding
   in a stable way (https://github.com/apache/airflow/issues/10118)
   The removed tests have success ratio of > 95% (20 runs without
   problems) and this has been verified a week ago as well,
   so it seems they are rather stable.
   
   There are literally few that are either failing or causing
   the Quarantined builds to hang. I manually reviewed the
   master tests that failed for last few weeks and added the
   tests that are causing the build to hang.
   
   Seems that stability has improved - which might be casued
   by some temporary problems when we marked the quarantined builds
   or too "generous" way of marking test as quarantined, or
   maybe improvement comes from the #10368 as the docker engine
   and machines used to run the builds in GitHub experience far
   less load (image builds are executed in separate builds) so
   it might be that resource usage is decreased. Another reason
   might be Github Actions stability improvements.
   
   We might still add failing tests back as soon we see them behave
   in a flaky way.
   
   The remaining quarantined tests that need to be fixed:
    * test_cli_webserver_background (often hangs the build)
    * test_retry_handling_job
    * test_clear_multiple_external_task_marker
    * test_should_force_kill_process
   
   Also - since those quarantined tests are failing more often
   the "num runs" to track for those has been decreased to 10
   to keep track of 10 last runs only.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   


----------------------------------------------------------------
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.

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


Reply via email to