Taragolis commented on PR #29035: URL: https://github.com/apache/airflow/pull/29035#issuecomment-1398885650
> No -not skipped - simply a bad timing /flaky test: > > ``` > Failed to reconnect to scheduler after 30.00 seconds, closing client > ``` Technically we should not grab this record. We grab logs and check it inside `with caplog.at_level(...)` and clear previously captured logs. So it could be: 1. A problem with `caplog` fixture, will check maybe same issue created in pytest 2. It is possible that `distributed` change some logging configuration during execution 3. Some part of Airflow logging -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
