fuzz: Return chrono point from ConsumeTime(), Add ConsumeDuration() #34337

pull maflcko wants to merge 2 commits into bitcoin:master from maflcko:2601-fuzz-chrono changing 5 files +15 −11

maflcko commented at 11:38 am on January 19, 2026: member

Returning a raw i64 is a bit confusing when it comes to chrono types. For example, in the addrman fuzz tests, the time_penalty is not a time point, but a duration.

Also, all call-sites assume second resolution right now, so document that better by returning NodeSeconds from ConsumeTime(...) and std::chrono::seconds from ConsumeDuration(...).

fuzz: Use min option in ConsumeTime

This is less code and also required for the next commit.

faa5a9ebad

DrahtBot renamed this:
~~fuzz: Return chrono point from ConsumeTime(), Add ConsumeDuration()~~
fuzz: Return chrono point from ConsumeTime(), Add ConsumeDuration()
on Jan 19, 2026
DrahtBot added the label Fuzzing on Jan 19, 2026
DrahtBot commented at 11:39 am on January 19, 2026: contributor

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage & Benchmarks

For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/34337.

Reviews

See the guideline for information on the review process. A summary of reviews will appear here.

fuzz: Return chrono point from ConsumeTime(), Add ConsumeDuration()

A chrono time point is a bit more type-safe than a raw i64.

Also, add a dedicated helper for plain chrono durations.

fa33ca66b2