OS X WebdriverIO tests have legitimate failures

[BenHenning]

Check for duplicates

• I have searched for similar issues before opening a new one.

Description

See #745. With a bunch of attempts at trying to stabilize the OS X tests, it seems two tests are legitimately failing.

Reproduction steps

Not sure as I don't have a Mac. These tests seem to fail 100% of the time on CI from what I can observe now that other timing-related failures have been mitigated in #745.

Stack trace

1) Move start tests
       Start moving value blocks:
     Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/runner/work/blockly-keyboard-experimentation/blockly-keyboard-experimentation/main/test/webdriverio/test/dist/move_test.js)
      at listOnTimeout (node:internal/timers:581:17)
      at process.processTimers (node:internal/timers:519:7)

  2) Scrolling into view
       Insert scrolls new block into view:

      AssertionError: expected false to be true
      + expected - actual

      -false
      +true
      
      at Context.<anonymous> (file:///Users/runner/work/blockly-keyboard-experimentation/blockly-keyboard-experimentation/main/test/webdriverio/test/dist/scroll_test.js:75:25)
      at Generator.next (<anonymous>)
      at fulfilled (file:///Users/runner/work/blockly-keyboard-experimentation/blockly-keyboard-experimentation/main/test/webdriverio/test/dist/scroll_test.js:9:58)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Screenshots

No response

Browsers

No response

[cpcallen]

Unfortunately neither of these failures reproduce locally for me.

I believe that the timeout, like most of the timeout failures we are seeing, is due to some kind of race condition that occasionally causes a webdriverio request get lost, leaving the test waiting for the browser to report that the action has finished (while the browser obliviously sits and twiddles its thumbs waiting for the next request).

This might also explain the AssertionError.