-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yet another attempt to fix flakey test_disable_logging
test
#36455
Yet another attempt to fix flakey test_disable_logging
test
#36455
Conversation
Let's see. We can merge it and retry the GCP change |
Strange thing it only happened in main and not in any PR and I have no idea why yet. But I will also take a look later today to see what difference was there |
Reopened with full tests needed |
merged. Let's see in main first ad then re-apply the GCP backcompat in main :) |
Looks like the fix worked . Good one @Taragolis ! (though we still do not know why it happened :). |
Remove back-compatibility code for stackdriver now that we are at >= 2.6.0. This caused problems recently with flaky / leaking tests but hopefully apache#36455 fixed the triggering mechanism for that flaky test and this one should succeed now.
Remove back-compatibility code for stackdriver now that we are at >= 2.6.0. This caused problems recently with flaky / leaking tests but hopefully #36455 fixed the triggering mechanism for that flaky test and this one should succeed now.
Remove back-compatibility code for stackdriver now that we are at >= 2.6.0. This caused problems recently with flaky / leaking tests but hopefully apache#36455 fixed the triggering mechanism for that flaky test and this one should succeed now.
This one revert approach which was used in #26973 but replaced by
caplog
duringunittests
->pytest
migration.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.