Repository navigation
First Fin-FinAck Support - #46
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #46 +/- ##
==========================================
+ Coverage 63.74% 69.13% +5.39%
==========================================
Files 23 24 +1
Lines 3194 3833 +639
==========================================
+ Hits 2036 2650 +614
- Misses 1158 1183 +25 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Bluefin throughput bench (macOS) ✅ PASSConfig: 5 run(s) × 2 conn(s) on Client throttle: 25 µs sleep every 3000 sends Retries: 4 of 5 run(s) needed retry (+6 extra attempt(s)). See per-run table. why retries vary across runsHosted CI runners occasionally land on a deeply contended host where both bench peers get starved and a run produces 0 GOOD conns despite no actual code regression. To absorb this without weakening the gate, this job uses an asymmetric retry policy (current values:
The retry budget is per-run and only shrinks across attempts: once a partial-good attempt has been observed in a run, that run is locked to the partial budget for the rest of its attempts -- it can never be promoted to the larger 0-good budget by a later attempt happening to collapse to 0. Only the final attempt's data is committed to the aggregate stats; earlier attempts' logs are still on disk under the run's So the same code can show 0, 1, or 2 retries on different CI runs purely from runner-allocation luck. The Aggregate
Per-run
A "good conn" delivered ≥ 700 MB before idle timeout. |
Uh oh!
There was an error while loading. Please reload this page.