| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The event loop delay histogram can record a zero-valued sample when two successive clock reads observe the same effective time. Keep checking that samples were recorded, but do not require the minimum sample to be positive. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> Assisted-by: openai:gpt-5.5
|
Added request-ci label for #63100, so that it can be merged |
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #63387 +/- ##
==========================================
- Coverage 90.06% 90.05% -0.02%
==========================================
Files 714 714
Lines 225629 225648 +19
Branches 42702 42698 -4
==========================================
- Hits 203211 203202 -9
+ Misses 14232 14224 -8
- Partials 8186 8222 +36 see 64 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The test-performance-eventloopdelay test can fail intermittently after
recording samples if one event loop delay sample is 0.
HDR histograms allow 0 values, and hdr_min() returns 0 when bucket 0 has
a count. This can happen when two successive uv_hrtime() reads observe the
same effective clock value.
This updates the test to keep requiring recorded samples while allowing
histogram.min to be 0.
Refs: https://github.com/nodejs/reliability/blob/main/reports/2026-05-17.md#jstest-failure
Assisted-by: openai:gpt-5.5