Skip to content

[BUG]: Rename property/test_schema.py to fix pytest import collision #6272

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.

Sign up for GitHub

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

Jump to bottom
Open
majiayu000 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[BUG]: Rename property/test_schema.py to fix pytest import collision #6272

majiayu000 wants to merge 1 commit into from

Conversation

@majiayu000
Copy link

@majiayu000 majiayu000 commented Jan 30, 2026

Rename test_schema.py to test_collection_schema.py to fix pytest import collision. Fixes #6031

@majiayu000
[BUG]: Rename property/test_schema.py to fix pytest import collision
9a7b7dd 
Rename chromadb/test/property/test_schema.py to test_collection_schema.py
to avoid import collision with chromadb/test/api/test_schema.py.

Fixes chroma-core#6031

Signed-off-by: majiayu000 <1835304752@qq.com>
@github-actions
Copy link

github-actions bot commented Jan 30, 2026

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@propel-code-bot
Copy link
Contributor

propel-code-bot bot commented Jan 30, 2026

The change specifically renames chromadb/test/property/test_schema.py to chromadb/test/property/test_collection_schema.py so pytest no longer confuses it with chromadb/test/api/test_schema.py, resolving issue #6031 without altering the underlying test logic.

Affected Areas

• chromadb/test/property/test_collection_schema.py

This summary was automatically generated by @propel-code-bot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Bug]: ERROR collecting chromadb/test/property/test_schema.py

1 participant

@majiayu000