Skip to content

Remove backcompat code for stackdriver#36442

Merged
potiuk merged 1 commit into
apache:mainfrom
potiuk:remove-backcompat-stackdriver-code
Dec 28, 2023
Merged

Remove backcompat code for stackdriver#36442
potiuk merged 1 commit into
apache:mainfrom
potiuk:remove-backcompat-stackdriver-code

Conversation

@potiuk

@potiuk potiuk commented Dec 27, 2023

Copy link
Copy Markdown
Member

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.rst or {issue_number}.significant.rst, in newsfragments.

@potiuk potiuk added the full tests needed We need to run full set of tests for this PR to merge label Dec 27, 2023
@boring-cyborg boring-cyborg Bot added area:logging area:providers provider:google Google (including GCP) related issues labels Dec 27, 2023
@potiuk potiuk force-pushed the remove-backcompat-stackdriver-code branch from 7a3ba7e to 6462d32 Compare December 27, 2023 09:40

@dirrao dirrao left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@potiuk

potiuk commented Dec 27, 2023

Copy link
Copy Markdown
Member Author

Well. I am puzzled ... It seem the previously seen log error is gone... Let me run it few more times.

@potiuk potiuk closed this Dec 27, 2023
@potiuk potiuk reopened this Dec 27, 2023
@Taragolis

Copy link
Copy Markdown
Contributor

Well. I am puzzled ... It seem the previously seen log error is gone... Let me run it few more times.

There more you look on the flakey error the less chance that it appear again 🤣

@potiuk

potiuk commented Dec 27, 2023

Copy link
Copy Markdown
Member Author

There more you look on the flakey error the less chance that it appear again 🤣

Very much so: 🐻

@potiuk

potiuk commented Dec 27, 2023

Copy link
Copy Markdown
Member Author

Seems like main started to fail after merging the other PR - let's see if #36453 will fix it again.

@potiuk potiuk force-pushed the remove-backcompat-stackdriver-code branch from 6462d32 to 55b9fe9 Compare December 27, 2023 15:01
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.
@potiuk potiuk force-pushed the remove-backcompat-stackdriver-code branch from 55b9fe9 to 3d9ff56 Compare December 28, 2023 01:17
@potiuk potiuk changed the title Reproduce asyncio failure with stackdriver leaking pytest fixture tasks Remove backcompat code for stackdriver Dec 28, 2023
@potiuk

potiuk commented Dec 28, 2023

Copy link
Copy Markdown
Member Author

Right - we should be able to merge that one now after @Taragolis improved log filtering.

@hussein-awala hussein-awala left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh finally

@potiuk potiuk merged commit 49ce3ed into apache:main Dec 28, 2023
@potiuk potiuk deleted the remove-backcompat-stackdriver-code branch December 28, 2023 01:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:logging area:providers full tests needed We need to run full set of tests for this PR to merge provider:google Google (including GCP) related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants