pub struct ResolverStats {Show 13 fields
pub built: usize,
pub submitted: usize,
pub posted: usize,
pub popped: usize,
pub failed_operations: usize,
pub failed_submits: usize,
pub expired_waits: usize,
pub empty_wakes: usize,
pub signals: usize,
pub reorderings: usize,
pub deferrals: usize,
pub barrier_holds: usize,
pub partial_transfers: usize,
}Expand description
What a resolution actually did, readable while the resolver is registered.
A test that narrows the config to isolate one freedom needs to know the freedom was exercised; otherwise a green run means only that the seed never took that branch. These counters are how a test asserts against the run rather than against the configuration.
Fields§
§built: usizeOperations built (any Build* call that returned success).
submitted: usizeOperations moved from built to submitted.
posted: usizeCompletions posted to the completion queue.
popped: usizeCompletions handed to a PopIoRingCompletion.
failed_operations: usizePosts that carried a failure result (RS-P-3 exercised).
failed_submits: usizeSubmits declined, leaving built operations queued (RS-P-7).
expired_waits: usizeWaits answered as expired (RS-P-4).
empty_wakes: usizeWaits answered successfully with nothing poppable (RS-P-5).
signals: usizeEvent signals raised (RS-P-6; zero when no event is attached).
reorderings: usizePosts that took something other than the oldest unresolved operation
(RS-P-2 exercised – reordering actually happened, as distinct from
having been permitted).
deferrals: usizeTimes an operation was left unresolved by a consultation (RS-P-1
exercised – something actually pended).
barrier_holds: usizeTimes a drain-flagged operation was held back because something queued
before it was still unresolved (RS-C-4 actually bit, as distinct from
having been vacuously satisfied).
partial_transfers: usizeSuccessful transfers reported short under RS-P-8.