This repository has been archived by the owner on Apr 3, 2020. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Backport] Allow forcing TestWebServer to use a specific port number.
Original commit message: Commit c4a3f88 ("TestWebServer needs to use a free port") has caused TestWebServer to use a random port number in each invocation. This does not play well with tests that assume the server will be running on a specific port (for example, an HTML asset trying to do XHR whose contents cannot be changed at runtime). start() and startSsl() can now be passed an optional port number; if it is being used, the server will fail to start like it did before the commit mentioned above. R=hush@chromium.org, yfriedman@chromium.org Review URL: https://codereview.chromium.org/666513002 Cr-Commit-Position: refs/heads/master@{#300151} This is required for org.xwalk.runtime.client.test.CrossOriginXhrTest and org.xwalk.runtime.client.embedded.test.CrossOriginXhrTest to work again in Crosswalk after moving to M39, as those tests require TestWebServer to be running on a specific port. BUG=XWALK-2755
- Loading branch information