The FSM suite retries certain CRUD operations on receiving a DatabaseDropPending error from the server. In build failures with multiple dropDatabase invocations and timeout errors on CRUD operations, it would be useful to know when the CRUD operation started. One place where this information would help is in the following log message:

insert command failed due to the plan_cache_drop_database database being marked as drop-pending. Waiting for th
e latest operation to become majority confirmed before trying again.

This log message is printed here:

https://github.com/mongodb/mongo/blob/0966ba7c98dcd47d6fff753cf380d1c38c2c3d2b/jstests/libs/override_methods/implicitly_retry_on_database_drop_pending.js#L153