| collection_enabled.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
5882 |
- |
| collection_enabled_bin.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
5657 |
- |
| common |
|
|
- |
| custom_distribution_buffered.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2463 |
- |
| dual_labeled_counter_metric.rs |
|
2228 |
- |
| health_ping.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
4327 |
- |
| health_ping_file_overwrite.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
3105 |
- |
| init_fails.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2384 |
- |
| interruptible_shutdown.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
5147 |
- |
| labeled_metrics.rs |
|
2213 |
- |
| memory_distribution_buffered.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2837 |
- |
| metric_metadata.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
3601 |
- |
| near-empty-c0ffee-db.safe.bin |
|
338 |
- |
| never_init.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2111 |
- |
| no_time_to_init.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2298 |
- |
| overflowing_preinit.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
3114 |
- |
| persist_ping_lifetime_nopanic.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
1232 |
- |
| schema.rs |
|
6994 |
- |
| signaling_done.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
3607 |
- |
| simple.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2559 |
- |
| test-delayed-ping-data.sh |
|
1633 |
- |
| test-enabled-pings.sh |
|
1585 |
- |
| test-mps-delay.sh |
|
1680 |
- |
| test-pending-gets-removed.sh |
|
1527 |
- |
| test-ping-lifetime-flush.sh |
|
1599 |
- |
| test-shutdown-blocking.sh |
|
763 |
- |
| test-thread-crashing.sh |
|
1106 |
- |
| timing_distribution_buffered.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2911 |
- |
| timing_distribution_single_sample.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
2186 |
- |
| upload_timing.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
7587 |
- |
| uploader_capabilities.rs |
This integration test should model how the RLB is used when embedded in another Rust application
(e.g. FOG/Firefox Desktop).
We write a single test scenario per file to avoid any state keeping across runs
(different files run as different processes). |
3828 |
- |