zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks.
I manage to reproduce the test failure quite consistently while doing code coverage with:
cargo llvm-cov --test interceptors
Output:
running 3 tests
test downsampling_config_error_wrong_strategy - should panic ... ok
test downsampling_by_keyexpr ... FAILED
test downsampling_by_interface ... ok
failures:
---- downsampling_by_keyexpr stdout ----
thread 'downsampling_by_keyexpr' panicked at zenoh/tests/interceptors.rs:132:17:
The test failed on the ke`test/downsamples_by_keyexp/20hz` at the rate of 0
Sometimes I also get:
running 3 tests
test downsampling_config_error_wrong_strategy - should panic ... ok
test downsampling_by_interface ... FAILED
test downsampling_by_keyexpr ... ok
failures:
---- downsampling_by_interface stdout ----
thread 'downsampling_by_interface' panicked at zenoh/tests/interceptors.rs:132:17:
The test failed on the ke`test/downsamples_by_interface/10hz` at the rate of 0
failures:
downsampling_by_interface
test result: FAILED. 2 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 7.05s
Mallets
commented
1 week ago
I manage to reproduce the test failure quite consistently while doing code coverage with:
Output:
Sometimes I also get:
Zenoh:
Target platform: