stacks-network / stacks-network/stacks-core

Flaky test: `test_bloom_counter_is_invertible_over_iterations`

Open
#3,579 3 comments 0 reactions 1 assignee View on GitHub

@jcnelson is already working on this.

Since Feb 21, 2023.

icebox testing
Dominant language
Rust
Stars
3.1k
Forks
762
Avg merge
4d 6h
Merged PRs (30d)
76

Description

Describe the bug

In the CI run for #3511 -- unit-tests failed due to an unrelated test failure:

#10 6011.6 ---- util_lib::bloom::test::test_bloom_counter_is_invertible_over_iterations stdout ----
#10 6011.6 Add 4096 items for pass 0
#10 6011.6 fp_count = 0, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0
#10 6011.6 Add 4096 items for pass 1
#10 6011.6 fp_count = 1, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0.0001220703125
#10 6011.6 Remove 4096 items from pass 0
#10 6011.6 fp_count = 0, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0
#10 6011.6 Add 4096 items for pass 2
#10 6011.6 fp_count = 1, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0.0001220703125
#10 6011.6 Remove 4096 items from pass 1
#10 6011.6 fp_count = 0, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0
#10 6011.6 Add 4096 items for pass 3
#10 6011.6 fp_count = 0, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0
#10 6011.6 Remove 4096 items from pass 2
#10 6011.6 fp_count = 4, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0.00048828125
#10 6011.6 Add 4096 items for pass 4
#10 6011.6 fp_count = 9, num_items = 8192, err_rate = 0.001, calculated_error_rate = 0.0010986328125
#10 6011.6 thread 'util_lib::bloom::test::test_bloom_counter_is_invertible_over_iterations' panicked at 'assertion failed: calculated_error_rate <= err_rate', src/util_lib/bloom.rs:829:13

This looks like test flake

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.