ashb commented on PR #28077: URL: https://github.com/apache/airflow/pull/28077#issuecomment-1336191067
My idea is a Two phase approach, similar to how we did... Typing? in the past. And I call it a ratchet. The first step is to capture how many warnings each test file produces, and then we fail ci if any new warnings are issued. The next step is once a file doesn't have any warnings there is a way of making pytest treat warnings as failure (I think we do it in one place in our test site right now). I noticed the sheer number of warnings when looking at the bug fix for rc3: it's way up from where I remember it, and it was only my list to look at next week. I suspect over half are from one of two helper funcs in our test suite! -- 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]
