o-nikolas commented on PR #32612: URL: https://github.com/apache/airflow/pull/32612#issuecomment-1636525176
> BTW. This is a constant risk - influx of tests that are flaky. I personally think that this is something that is difficult to handle, but it's a different story that we KNOW that a test can be flaky.. in such case we should make all the efforts to try to test it in various configurations. > > And we have tools for that: > > * close/reopen a test few times to checkl > > * apply "use public runners" and repeat it > > Those are the tools all commiters have to "try" a risky PR to try to see if the change that has a possible side-effect is "sound enough", so that it does not introduce a problem. That's a great idea to test on public runners, I'll keep that in my back pocket for future changes. I'll close/reopen the tests a few times on public runners. So far the test is running quite well and is not even close to the slowest of the CLI test suite :smile:  -- 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
