Hello Vishnu, We do not see the attachment so no idea which tests you are referring to.
Generally speaking - we treat our main "No broken window" policy - i.e. sometimes things are breaking and we attempt to fix it quickly. If you would like to help with that and help such failing tests - you can join #internal-airlfow-ci-cd channel on Airflow Slack and every time there is a failure, you can volunteer to help with such an issue. When it comes to individual tests - if you follow Contributor's guide and setup the dev environment (particularly breeze docker compose environment) https://github.com/apache/airflow/blob/main/contributing-docs/README.rst - it is designed to avoid "works for me" syndrome where your local setup, old dependencies, lack of system dependencies,different machine cause failures on your local environment. Breeze is designed to provide everyone the same dockerized environment where you should be able to replicate the same tests that are run in CI and they **should** work in the same way. If there are some differences in your environment that cause it (hard to say what is failing because we do not see the screenshot of yours) then you should be able to replicate non failing behaviour in breeze and possibly even you could try to analyse the differences and maybe even propose PRs to improve portability in your environment. This documentation https://github.com/apache/airflow/tree/main/contributing-docs/testing describes all the kinds of tests we have, how to replicate locally exactly the same that works in CI. There are also some tests that have side-effects or rely on side-effects of other tests - when you see such a test failing when run in isolation, it's a great idea to attempt to find and fix the issue. This is a nice contribution. J. On Fri, Dec 27, 2024 at 9:00 PM Vishnu Chilukoori <vish.chiluko...@gmail.com> wrote: > Hi Devs, > > I was running core tests on the main branch of airflow and noticed a few > tests are failing. Is this expected? > > [image: development_branch_unstable_test_runs.png] > > -- > Regards, > Vishnu Chilukoori >
