Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Service Arch
Description
There doesn't seem to be a way to hang at a failpoint in the server code, do something in my JS test, and then "release" the failpoint to let the server code run past the failpoint, but still keep the failpoint on so that if the server code reaches the failpoint again, it will still get stopped again (We currently need to turn on a second failpoint that's after the first failpoint, then turn off the first failpoint, wait for the second failpoint to be hit, turn the first failpoint back on, and then turn the second failpoint off). Could this be added to configureFailpoint?