quickwit-oss / quickwit-oss/quickwit
flaky test test_rate_limiter_acquire
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
---- rate_limiter::tests::test_rate_limiter_acquire stdout ----
thread 'rate_limiter::tests::test_rate_limiter_acquire' panicked at quickwit-common/src/rate_limiter.rs:173:9:
assertion failed: !rate_limiter.acquire_bytes(ByteSize::kb(20))
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::panicking::panic
3: quickwit_common::rate_limiter::tests::test_rate_limiter_acquire
4: quickwit_common::rate_limiter::tests::test_rate_limiter_acquire::{{closure}}
5: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failures:
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 running rate_limiter::tests::test_rate_limiter_acquire and inspect quickwit-common/src/rate_limiter.rs at line 173, where the assertion fails. Reproduce the failure and determine why the acquire_bytes(ByteSize::kb(20)) assertion is flaky; done means the test runs reliably without intermittent failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100