This is required to make sure that the WebCore thread's message
handlers are ready to receive settings.
Change-Id: I2c4df95e3b7409535b739ada957d93a7e6cd78d6
It avoids OOM issues by dumping the memory to the DB every
few hundred tests and then reading them in chunks when
generating summaries, etc.
Change-Id: I5f63d960d456f17e9f2189230a7ae0ca5607ce51
Currently DumpRenderTree2 serves HTTP tests on http://localhost:8080.
Some of the tests hardcode 'http://127.0.0.1:8000' for resources, so
we must use this scheme and port for the requests to be same-origin.
This fixes LayoutTest http/tests/appcache/credential-url.html
Change-Id: I2a9c402fc7b0e0b62eb4a278d67ac0e63ef96e8b
When adding JavaScript interfaces to a WebView, they must be passed to
the WebView constructor, rather than to
WebView.addJavascriptInterface() if they are to be used immediately
without the risk of race conditions.
This fixes LayoutTest
http/tests/appcache/crash-when-navigating-away-then-back.html
This was fixed for DumpRenderTree in
https://android-git.corp.google.com/g/23804
Change-Id: I1581d6d6cfc1b35be1ec2f2e5b5b944da2b4b935
Currently, DumpRenderTree2 asigns the following result codes
{PASS, FAIL_RESULT_DIFFERS, FAIL_NO_EXPECTED_RESULT, FAIL_TIMED_OUT,
FAIL_CRASHED}
This is not strictly correct, as a test may fail for any of three
reasons - crashing, timing out, or the the result not being as
expected. Therefore, it's possible for a test to fail even if the
result is as expected.
This patch updates AbstractResult to handle each of the three reasons
for failure separately. We then test all three to determine if the
test has passed.
This allows us to correctly report whether or not the result differs
from expected for a failing test.
Change-Id: I7adcfe72c4dd0bd3de2e1b868d9807be6eb5bddf
There was a deadlock when ConnectionHandler exited the loop in SocketPipeThread, and would call the onFinishedCallback, which called the synchronized method in Forwarder that would
deadlock. Changing the Forwarder class solved the issue and made it more efficient.
Change-Id: I947450a19573f2e88274b1ebc7b77d4df6afffa7
The revision number is taken from external/webkit/WEBKIT_MERGE_REVISION and is served to the java code by apache server. To be able to do that, the new alias directive had to be
added to the run_apache2.py script.
Bug: 2889572
Change-Id: Ie3d147e4d8ea9edd0144b819152121563b8bd759
Before, if a crash was detected, but the "Force quit" dialog remained on the screen, sending the intent to restart the executor would do nothing. It's fixed now with default
uncaught exception handler. Also, when we catch the uncaught exception, we can restart the executor straight away, without waiting for the time-out.
Change-Id: I2f0b4b5f2abd180ff518f1a40ad1294bed2f7f67
The call would deadlock because lines 62-67 in ConnectionHandler were in the synchronized block. The is.read() would block and therefore call to shutdown() would block too.
is.read()
would never unblock because the stream was ready to be closed, and it needs to be done so from shutdown(). Removing the synchronized block fixes it and is save, as it was not
needed here.
Change-Id: I3326098c47ee18c4eabaa8510b27ca82debce360
It creates the sockets on the device that allow DumpRenderTree2 to get tests from the server running on the remote machine. Communication happens through the adb.
Change-Id: I7f26ffc78195b6c5f4d423a57d5ee5f0f4a9c615
