quickwit-oss / quickwit-oss/quickwit
test_scheduler_scheduling_and_control_loop_apply_plan_again fails occasionally
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Describe the bug
I ran all our tests many time over night to verify my fix, but as a side effect I collected some of other failures. This test failed in 2.2% of the runs.
running 1 test
test scheduler::tests::test_scheduler_scheduling_and_control_loop_apply_plan_again ... FAILED
failures:
failures:
scheduler::tests::test_scheduler_scheduling_and_control_loop_apply_plan_again
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 10 filtered out; finished in 0.21s
thread 'scheduler::tests::test_scheduler_scheduling_and_control_loop_apply_plan_again' panicked at 'assertion failed: `(left == right)`
left: `4`,
right: `3`', quickwit-control-plane/src/scheduler.rs:672:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
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 with scheduler::tests::test_scheduler_scheduling_and_control_loop_apply_plan_again in quickwit-control-plane/src/scheduler.rs, especially the assertion at line 672. Run this test repeatedly to reproduce the intermittent left-4/right-3 failure, then inspect the scheduler control-loop behavior around the test. Done means the test passes reliably across repeated runs without weakening its intended assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100