New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wptrunner] Guard against empty command_queue in BrowserManager.send_message #5774
[wptrunner] Guard against empty command_queue in BrowserManager.send_message #5774
Conversation
Build BROKENStarted: 2017-08-11 23:43:50 View more information about this build on: |
Firefox (nightly channel)Testing web-platform-tests at revision b31f26a |
Chrome (unstable channel)Testing web-platform-tests at revision b31f26a |
I think the code here is just broken; |
…message This happens when sending the message 'init_failed' and causes wptrunne to hang. This patch is something I need to keep the tests running, but there is probably a cleaner solution.
c2d999b
to
5559e18
Compare
@jgraham apologies for the really long latency on this - I just updated the patch with your suggestion. |
(Tracked in web-platform-tests/results-collection#142) |
Build PASSEDStarted: 2017-10-11 20:52:17 View more information about this build on: |
Looks like the earlier test failure was a fluke, this should be ready to go now. |
I thought I'd removed the use of |
This happens when sending the message
'init_failed'
and causes wptrunner to hang sinceself.command_queue
doesn't exist at that point.This patch is something I'm using to keep wptrunner from getting stuck, but there is probably a cleaner solution.
This change is