The test occasionally fails because it assumes log ID 6825401 will be written after a collection drop. If an index-build quorum-checker thread still holds a strong reference of the collection dropped, the collection instance is reused from dropPendingCollections, so the log line never appears—even though the PIT read and the re-used collection instance is perfectly correct. Removing the assertion on log 6825401 eliminates the nondeterminism.

In short, point_in_time_lookups_drop_pending.js is flaky when checking that a PIT read creates a new instance for the collection after a drop.