Skip to content
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

Fix side effect of not tearing down mongo hook in tests #46291

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Jan 30, 2025

The MongoClient apparently starts a separate thread that runs an active loop that performs sleep every 0.5 second. MongoClient is stored in the Hook and hooks/test_mongo.py stored the hook as object in the test class, which means that the thread has not been torn down and continued to run after mongo tests completed.

Subsequently any test that was mocking time.sleep (and skipping waiting) had been spammed by mongo client thread calling sleep() - potentially many times.

Earlier attempts to fix this had not succeeded - so they are reverted now as part of this PR, as the original patching of sleep was much nicer there.

Revert "Make racy test test_start_pod_startup_interval_seconds less racy (#46282)"

This reverts commit 60f0abf.

Revert "Make azure test less flaky/racy (#46281)"

This reverts commit ae55e22.


^ 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.

The MongoClient apparently starts a separate thread that runs an
active loop that performs sleep every 0.5 second. MongoClient
is stored in the Hook and hooks/test_mongo.py stored the hook
as object in the test class, which means that the thread has not
been torn down and continued to run after mongo tests completed.

Subsequently any test that was mocking time.sleep (and skipping waiting)
had been spammed by mongo client thread calling sleep() -
potentially many times.

Earlier attempts to fix this had not succeeded - so they are reverted
now as part of this PR, as the original patching of sleep was much nicer
there.

Revert "Make  racy test test_start_pod_startup_interval_seconds less racy (apache#46282)"

This reverts commit 60f0abf.

Revert "Make azure test less flaky/racy (apache#46281)"

This reverts commit ae55e22.
@potiuk potiuk added full tests needed We need to run full set of tests for this PR to merge canary When set on PR running from apache repo - behave as canary run labels Jan 30, 2025
@potiuk potiuk closed this Jan 30, 2025
@potiuk potiuk reopened this Jan 30, 2025
@ashb
Copy link
Member

ashb commented Jan 30, 2025

It does WHAT? 🤯

@potiuk
Copy link
Member Author

potiuk commented Jan 30, 2025

It does WHAT? 🤯

Yep. 🤯

@potiuk potiuk merged commit a50d2e5 into apache:main Jan 30, 2025
116 of 154 checks passed
@potiuk potiuk deleted the fix-side-effect-of-mongo-hook branch January 30, 2025 16:39
@jscheffl
Copy link
Contributor

Wow, great catch!

@potiuk
Copy link
Member Author

potiuk commented Jan 31, 2025

Wow, great catch!

🐟

niklasr22 pushed a commit to niklasr22/airflow that referenced this pull request Feb 8, 2025
The MongoClient apparently starts a separate thread that runs an
active loop that performs sleep every 0.5 second. MongoClient
is stored in the Hook and hooks/test_mongo.py stored the hook
as object in the test class, which means that the thread has not
been torn down and continued to run after mongo tests completed.

Subsequently any test that was mocking time.sleep (and skipping waiting)
had been spammed by mongo client thread calling sleep() -
potentially many times.

Earlier attempts to fix this had not succeeded - so they are reverted
now as part of this PR, as the original patching of sleep was much nicer
there.

Revert "Make  racy test test_start_pod_startup_interval_seconds less racy (apache#46282)"

This reverts commit 60f0abf.

Revert "Make azure test less flaky/racy (apache#46281)"

This reverts commit ae55e22.
ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Feb 17, 2025
The MongoClient apparently starts a separate thread that runs an
active loop that performs sleep every 0.5 second. MongoClient
is stored in the Hook and hooks/test_mongo.py stored the hook
as object in the test class, which means that the thread has not
been torn down and continued to run after mongo tests completed.

Subsequently any test that was mocking time.sleep (and skipping waiting)
had been spammed by mongo client thread calling sleep() -
potentially many times.

Earlier attempts to fix this had not succeeded - so they are reverted
now as part of this PR, as the original patching of sleep was much nicer
there.

Revert "Make  racy test test_start_pod_startup_interval_seconds less racy (apache#46282)"

This reverts commit 60f0abf.

Revert "Make azure test less flaky/racy (apache#46281)"

This reverts commit ae55e22.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers canary When set on PR running from apache repo - behave as canary run full tests needed We need to run full set of tests for this PR to merge provider:cncf-kubernetes Kubernetes provider related issues provider:microsoft-azure Azure-related issues provider:mongo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants