quickwit-oss / quickwit-oss/quickwit

Flaky tests in quickwit-indexing crate

Open
#6,049 0 comments 0 reactions 1 assignee View on GitHub

@fulmicoton-dd is already working on this.

Since Dec 26, 2025.

bug flaky test
Dominant language
Rust
Stars
11.7k
Forks
597
Avg merge
2d 22h
Merged PRs (30d)
37

Description

Summary

Multiple tests in the quickwit-indexing crate are showing flaky behavior and consistent failures across test runs.

Flaky Tests

  • source::kafka_source::kafka_broker_tests::test_kafka_source_suggest_truncate - Shows flaky behavior (passed some runs, failed others)

Consistently Failing Tests (TRY 6 FAIL in all 4 test runs)

Pulsar Source Tests:

  • source::pulsar_source::pulsar_broker_tests::test_partitioned_topic_multi_consumer_ingestion
  • source::pulsar_source::pulsar_broker_tests::test_partitioned_topic_multi_consumer_ingestion_with_failover
  • source::pulsar_source::pulsar_broker_tests::test_partitioned_topic_single_consumer_ingestion
  • source::pulsar_source::pulsar_broker_tests::test_topic_ingestion
  • source::pulsar_source::pulsar_broker_tests::test_doc_batching_logic
  • source::pulsar_source::pulsar_broker_tests::test_multi_topic_ingestion

Kafka Source Tests:

  • source::kafka_source::kafka_broker_tests::test_kafka_source

Test Environment

All tests were run with make test-all and failed consistently across 4 separate runs.

Impact

These failures are blocking the test suite completion and may indicate issues with:

  • Pulsar broker connectivity/setup
  • Kafka broker connectivity/setup
  • Test environment reliability
  • Race conditions in source implementations

Next Steps

  1. Investigate Pulsar broker test setup and dependencies
  2. Review Kafka broker test configuration
  3. Check for timing/race condition issues
  4. Consider if tests need better isolation or cleanup

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.