-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Correctness 2026-01-26
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It is possible for resmoke configuration to happen more than once. I am not aware of all of the ways this can happen but we should probably tackle those eventually so this stuff can't bite us over and over. This happened in burn_in and caused one of the checks about duplicate configuration to fail.
I just reinitialize the module directory lists so they do not grow indefinitely as the configuration gets rerun.