-
Notifications
You must be signed in to change notification settings - Fork 2k
[TST]: fix concurrency bug in test_cross_version_persist #4770
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
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
| from typing import Dict, List | ||
|
|
||
| base_install_dir = tempfile.gettempdir() + "/persistence_test_chromadb_versions" | ||
| base_install_dir = ( |
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.
prior to this change, base_install_dir ended up being the same value for all workers spawned by pytest-xdist (which I would not expect), leading to the workers clobbering each other during installs
|
This PR updates the test utility for cross-version persistence to resolve a concurrency bug that appeared when running pytest-xdist. The base install directory for versioned package installs is now unique per test worker to prevent concurrent test processes from clobbering each other. This summary was automatically generated by @propel-code-bot |
…#4770) ## Description of changes Closes chroma-core#4263. ## Test plan _How are these changes tested?_ - [x] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust
Description of changes
Closes #4263.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rust