Fix the thread test to not be racy.

We shouldn't assume we know what order threads will be started in.
Running a debug build, it sometimes takes > 1ms to start the next

Change-Id: Icb7792f83809ad414cfcdf0828cdc198698deaf1
2 files changed
tree: aea80a1c9da052168144de89c0af988f6833f30c
  2. build/
  3. oat_process/
  4. oat_runtime/
  5. src/
  6. test/
  7. tools/