WebDriver process killed before the Command.QUIT sent to it

[wpt-issue-mover]

Originally posted as w3c/wptrunner#175 by @lizzygao on 24 Mar 2016, 03:02 UTC:

Run the wptrunner and take the Chrome as the product, like this:

wptrunner --metadata=tests\ --tests=tests\ --binary="C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --product=chrome --webdriver-binary="C:\Users\ygao\bin\chromedriver.exe" --include=2dcontext --processes=1 --log-raw=log-raw.txt > test.txt

Some errors come up about:
URLError:
urlopen error [Errno 10061] No connection could be made because the target machine actively refused it

It caused by the WebDriver process (LocalServer.stop) is killed, and then the QUIT command sent to it (SeleniumProtocol.teardown)

This behavior is not suitable for the QUIT is never working on the WebDriver server side.

Is this an considering issue and being fixed?

[foolip]

I wonder if this might be why I'm seeing a failure when I invoke ./wpt run twice in CI: foolip#5

The second time it seems the port is taken and it just fails to connect.