qdrant / qdrant/qdrant

Flaky test `filtrable_hnsw_test::test_filterable_hnsw::case_1_nearest`

Open
#4,716 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted
Dominant language
Rust
Stars
34.7k
Forks
2.7k
Avg merge
1d 18h
Merged PRs (30d)
187

Description

Last report

System error
blocks.len() = 18
thread 'filtrable_hnsw_test::test_filterable_hnsw::case_1_nearest' panicked at lib/segment/tests/integration/filtrable_hnsw_test.rs:257:5:
hits: 94 of 100
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Context

Date: 17.02.2025 09:52

Flaky failure run

Commit

OS: macos-latest

Branch: refs/pull/5996/merge

#5996

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with lib/segment/tests/integration/filtrable_hnsw_test.rs at line 257 and inspect the failure from the linked run at commit 1c2e6b845a4d286ddbd1df3f45ec7d3398e3c2dc. Re-run the test with RUST_BACKTRACE=1 and determine why it reports 94 of 100 hits on macos-latest. Done means the test reliably passes without the flaky nearest-neighbor failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
search, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.