potiuk commented on a change in pull request #6472: [AIRFLOW-6058] Running tests with pytest URL: https://github.com/apache/airflow/pull/6472#discussion_r350650581
########## File path: tests/pytest.ini ########## @@ -0,0 +1,37 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +[pytest] +addopts = + -rasl + --cov=airflow/ + --cov-report html:airflow/www/static/coverage/ + --ignore=tests/dags/test_dag_serialization.py +; This will treat all tests as flaky +; --force-flaky +norecursedirs = + tests/dags_with_system_exit + tests/test_utils + tests/dags_corrupted +faulthandler_timeout=180 +log_print = True +log_level = INFO +filterwarnings = + ignore::DeprecationWarning + ignore::PendingDeprecationWarning + ignore::RuntimeWarning Review comment: I am all ok for filtering Deprecation warnings but only when we run regular PRs in CI. If we run tests locally, we should still see the warnings (that encourages to fix the warnings). I think there is very little value in warnings displayed in CI for regular PRs. Usually those will be the "other" warnings that you are not really interested in. Maybe, what could be done instead - we have the CRON build run daily where we already have a more comprehensive tests (for example we build the whole Docker image from the scratch and we always run Kubernetes tests no matter if any of kubernetes files changed). Maybe we could change it that Deprecation warnings are still displayed when you run tests locally and when you run CRON CI job, but not when you run regular PR. ---------------------------------------------------------------- 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] With regards, Apache Git Services
