client.thread fails due to flaky output order

I don't quite understand how it gets this order, but one one of my machines I have seen this failure in the client.thread test:

```
Output:
----------------------------------------------------------
PR 216931: client options are -paramx -paramy
inside app client.thread.exe
PR 198871 locking test......passed
client thread is alive
client thread is dying
PR 222812: client thread test passed
PR 210591: testing client transparency
client thread is alive
thread.appdll.dll process attach
loaded library
thread.appdll.dll process detach
i#1489 last-thread test
thank you for testing the client interface
TLS slot 0 is 0xbadcab42
TLS slot 1 is 0xbadcab43
TLS slot 2 is 0xbadcab44
TLS slot 3 is 0xbadcab45

Test time = 1.68 sec
----------------------------------------------------------
Test Fail Reason:
Required regular expression not found.Regex=[^PR 216931: client options are -paramx -paramy^M?
inside app client\.thread\.exe^M?
PR 198871 locking test\.\.\.\.\.\.passed^M?
client thread is alive^M?
client thread is dying^M?
PR 222812: client thread test passed^M?
thread\.appdll\.dll process attach^M?
loaded library^M?
PR 210591: testing client transparency^M?
client thread is alive^M?
thread\.appdll\.dll process detach^M?
i#1489 last-thread test^M?
thank you for testing the client interface^M?
TLS slot 0 is 0xbadcab42^M?
TLS slot 1 is 0xbadcab43^M?
TLS slot 2 is 0xbadcab44^M?
TLS slot 3 is 0xbadcab45^M?
$
```