https://chromium.googlesource.com/chromium/src/+/master/content/browser/wake_lock/wake_lock_browsertest.cc#80

These tests are sleeping to "resolve" asynchronous responses from the renderer. We should never ever ever do this as it is a source of flake.

Instead, these tests should use a test API to listen for state changes in the WakeLockServiceContext, and spin a runloop until state change occurs.