HangDumpChildProcesses very flaky

[nohwnd]

I increased timeouts, but it often fails with one of the .net core dmps being empty. NOt sure if that is recent regression there were more flaky tests before, for these I can repro locally but I see nothing wrong in the log.

maybe enabling the super verbose log of creating dump would tell us.

[nohwnd]

logDumpGeneration: false);

[nohwnd]

there is also race condition, if testhost does not start on time, we grab process 0 = Creating full dump of process Idle , and that is a problem because we are trying to dump something we don't own.