-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
ALL
-
STM 2021-03-08
-
1
Running the hang analyzer with no processes specified causes it to discover resmoke and send it a SIGUSR1 to dump info. When Resmoke receives a SIGUSR1 it invokes the hang analyzer targeting its subprocesses. Now there are two hang analyzers that will target the same mongo and mongods, creating attachment failures, overwriting output files, and sometimes hanging as well.
This doesn't happen in CI because we only target python processes, but it's intended that a local invocation without specifying processes should work.