This is a workaroud. Once the issue is resolved in Rust side, we should remove it. Fixes #895
These tests weren't running because with the old timer implementation time-outs were sometimes lost, and the test harness uses setTimeout to throw errors after a test has failed.