t2ym/reportage

[config] timeout for receiving ready from mediator is not recovered

Closed this issue · 1 comments

t2ym commented

[config] timeout for receiving ready from mediator is not recovered

Root Cause

  • In driver.js, recovery mechanism from a failure of receiving ready from mediator does not work as expected
    • As retryTimeout == mediatorReadyTimeout == 5, no timings of retrying
    • retryTimeout should be way larger than mediatorReadyTimeout
    • mediatorReadyTimeout should be smaller
  • It is under investigation where the connect message is lost
    • mediator-worker.js SharedWorker may have failed to receive the connect message
      • possibly due to highly flooded IPC traffic
    • driver.js gives up receiving the message too early

Reproducible Steps

  • Perform GUI test on examples/web-dev-server, which is highly loaded
  • mediator-bridge.html is opened but does not send ready to the opener app tab
  • Error message in the stalled app tab
target-app.js:5 http://127.0.0.7:3000/target-app.js loaded
driver.js:315 Error: DriverState:connecting.timeout: timeout for receiving ready
    at driver.js:309:24
doConnect @ driver.js:315

Fix

  • mediatorRetryTimeout 5s -> 1s
  • readyTimeout 5s -> 15s
t2ym commented

Remaining problems are handled in other issues