`1000ms` is a very long time for a computer, maybe this should be made shorter to make it less likely that a benchmark terminates before the attempt to abort it? Maybe another option could be to use `awaitBusy` on the benchmark status API to know when the benchmark actually started?