Add multithreaded concurrency coverage for cuVS-Lucene PyLucene tests
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
Summary
Add multithreaded concurrency coverage as a follow-up to NVIDIA/cuvs-lucene#174.
The current PyLucene end-to-end suite does not yet exercise concurrent operation.
Potential scope
- concurrent searches
- indexing while searches are active
- resource lifecycle and thread-safety behavior
The exact cases and acceptance criteria should be refined with the maintainers. Reuse the suite's deterministic correctness and execution-path checks where applicable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing PyLucene end-to-end test suite and reviewing the follow-up context in NVIDIA/cuvs-lucene#174. Run the current deterministic correctness and execution-path checks before discussing concurrent searches, indexing during searches, and resource lifecycle cases with maintainers. Done means the agreed multithreaded scenarios are covered with reliable thread-safety and correctness checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100