-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Remove backcompat code for stackdriver #36442
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
Conversation
7a3ba7e to
6462d32
Compare
dirrao
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Well. I am puzzled ... It seem the previously seen |
There more you look on the flakey error the less chance that it appear again 🤣 |
Very much so: 🐻 |
|
Seems like main started to fail after merging the other PR - let's see if #36453 will fix it again. |
6462d32 to
55b9fe9
Compare
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.
55b9fe9 to
3d9ff56
Compare
|
Right - we should be able to merge that one now after @Taragolis improved log filtering. |
hussein-awala
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh finally
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.
^ 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.rstor{issue_number}.significant.rst, in newsfragments.