[TST] Enable quantized spann in CI

[Sicheng-Pan]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Enable quantized spann in CI
• New functionality
  • N/A

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Migration plan

Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?

Observability plan

What is the plan to instrument and monitor this change?

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

[Sicheng-Pan]

• [TST] Enable quantized spann in CI #6750 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

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]

Enable quantized SPANN in CI with test tolerance and resource tuning updates

This PR primarily enables quantized SPANN behavior in CI distributed environments and stabilizes related tests. It updates distributed frontend sample configs to enable quantization for all tenants via tenants_with_quantization_enabled: ["*"], adjusts Kubernetes dev resource allocations (notably queryService, compactionService, and rustLogService CPU), and increases cluster CI runner size in .github/workflows/_python-tests.yml.

To reduce quantization-related flakiness, the PR updates property and schema tests to tolerate server-assigned/tuned SPANN values and quantized distance error bounds. In chromadb/test/property/invariants.py, distance validation now detects active quantization from serialized_schema and applies an absolute tolerance derived from vector norms and dimensionality. Additional test refinements include dimension range constraints in property strategies and acceptance of SegmentType::QuantizedSpann in Rust integration assertions.

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

[propel-code-bot]

No issues were identified; changes appear consistent with enabling quantized SPANN in CI and reducing test flakiness.

Status: No Issues Found | Risk: Low

Review Details

📁 10 files reviewed | 💬 0 comments

[sanketkedia]

Just confirming my understanding of the change - you have not yet enabled quantization in CI just made sure that if and when we do, the tests would pass successfully? Is that correct? And you would enable it in CI in a follow up PR?

[github-actions]

⚠️ The Helm chart was updated without a version bump. Your changes will only be published if the version field in k8s/distributed-chroma/Chart.yaml is updated.