tool.drcachesim.coherence timeout on appveyor

[derekbruening]

This happened once on Appveyor:

https://ci.appveyor.com/project/DynamoRIO/dynamorio/builds/29130585

[00:12:07]         Start 215: code_api|tool.drcachesim.coherence
[00:12:07] 215: Test command: C:\projects\dynamorio\build\build_debug-internal-32\bin32\drrun.exe "-s" "150" "-quiet" "-debug" "-use_dll" "C:/projects/dynamorio/build/build_debug-internal-32/lib32/debug/dynamorio.dll" "-exit0" "-stderr_mask" "0xC" "-msgbox_mask" "0" "-dumpcore_mask" "0x7d" "-staged" "-code_api" "-t" "drcachesim" "-ipc_name" "drtestpipe_coherence" "-coherence" "--" "C:/projects/dynamorio/build/build_debug-internal-32/suite/tests/bin/client.annotation-concurrency.exe" "client.annotation-concurrency.appdll.dll" "A" "4"
[00:12:07] 215: Test timeout computed to be: 150
[00:12:07] 215: 
[00:12:07] 215:     -------------------------------------------------------------------
[00:12:07] 215:      Performance for solving AX=B Linear Equation using Jacobi method
[00:12:07] 215:      Running on DynamoRIO
[00:12:07] 215:      Client version (null)
[00:12:07] 215:     ...................................................................
[00:12:07] 215: 
[00:12:07] 215:      Matrix Size :  512
[00:12:07] 215:      Threads     :  4
[00:12:07] 215: 
[00:12:07] 215: 
[00:12:07] 215:      Started iteration 1 of the computation...
[00:12:07] 215: 
[00:12:07] 215:      Finished computing current solution distance in mode 0.
[00:12:07] 215:      Mode changed to 0.
[00:12:07] 215: 
[00:12:07] 215:      Started iteration 2 of the computation...
[00:12:07] 215: 
[00:12:07] 215:      Finished computing current solution distance in mode 0.
[00:12:07] 215:      Mode changed to 0.
[00:12:07] 215: 
[00:12:07] 215:      Started iteration 3 of the computation...
[00:12:07] 215: 
[00:12:07] 215:      Finished computing current solution distance in mode 0.
[00:12:07] 215:      Mode changed to 0.
[00:12:31] 215: 
[00:12:31] 215:      Started iteration 4 of the computation...
[00:12:31] 215: 
[00:12:31] 215:      Finished computing current solution distance in mode 0.
[00:12:31] 215:      Mode changed to 0.
[00:12:31] 215: 
[00:12:31] 215:      Started iteration 5 of the computation...
[00:12:31] 215: 
[00:12:31] 215:      Finished computing current solution distance in mode 0.
[00:12:31] 215:      Mode changed to 0.
[00:13:09] 215: 
[00:13:09] 215:      Started iteration 6 of the computation...
[00:13:09] 215: 
[00:13:09] 215:      Finished computing current solution distance in mode 0.
[00:13:09] 215:      Mode changed to 0.
[00:13:09] 215: 
[00:13:09] 215:      Started iteration 7 of the computation...
[00:13:09] 215: 
[00:13:09] 215:      Finished computing current solution distance in mode 0.
[00:13:09] 215:      Mode changed to 0.
[00:13:09] 215: 
[00:13:09] 215:      Started iteration 8 of the computation...
[00:13:09] 215: 
[00:13:09] 215:      Finished computing current solution distance in mode 0.
[00:13:09] 215:      Mode changed to 0.
[00:13:09] 215: 
[00:13:09] 215:      Started iteration 9 of the computation...
[00:13:09] 215: 
[00:13:09] 215:      Finished computing current solution distance in mode 0.
[00:13:09] 215:      Mode changed to 0.
[00:13:34] 215: 
[00:13:34] 215:      Started iteration 10 of the computation...
[00:13:34] 222/259 Test #215: code_api|tool.drcachesim.coherence ...........................***Timeout 150.01 sec
[00:14:00] 	215 - code_api|tool.drcachesim.coherence (Timeout)

I happen to have a downloaded log from Nov 14 and this test is always taking over 40s:

[00:12:39] 223/259 Test #215: code_api|tool.drcachesim.coherence ...........................   Passed  120.66 sec
[00:24:49] 194/231 Test #189: code_api|tool.drcachesim.coherence ...........................   Passed  104.53 sec

We should either increase the timeout or shrink the test (latter sounds better).

Xref #3803 but here there is no #3320 assert.

[derekbruening]

This was addressed by #4059 where I shrunk all the drcachesim tests running the annotation app.