attempted to fix a timeout issue with this test by increasing the test's timeout to 360. It was pointed out that the test can sometimes take over 2 minutes to run, so an increase in the timeout might resolve the issue. It has not, and now the test takes 24 or 60 minutes before it times out, depending on whether test.timeout.factor is set to 4 or 10. I'm not sure what is controlling test.timeout.factor, but I'm seeing both these values used in failed test runs.
As part of the fix for this test, I suggest we also roll back the
and set the timeout to something reasonable. timeout=360 usually means 60 minutes, but sometimes 24. The longest successful test run I can see are on windowx-x64, which frequently is over 7 minutes, but always well under 8. So 10 minutes would be a good target timeout, which equates to timeout=144.