SERVER-135707ClosedWon't Fix

FP Safety 5/5: Restrict absolute failpoint wait API

h3. Background After T1-T4, no test waits on the absolute failpoint counter by accident. But nothing stops someone from writing {{fpb->waitForTimesEntered(1)}} again in the future. h3. What to do Change {{FailPoint::waitForTimesEntered}} so that absolute waits can't be written by accident. Evaluate three options and pick one: * (a) require an explicit \{{AbsoluteEntryCount\{n\}}} wrapper type * (b) make the method private, reachable only through {{FailPointEnableBlock}} * (c) rena

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification
bf-46466-postmortembf-postmortem