100100 2012-10-23 03:30:54 -0700 [Chromium] Running layout tests for Android should be more reliable 2013-04-08 11:02:53 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 96492 100944 100950 101233 101944 102245 103065 1 peter peter pasko pliard timvolodine oldest_to_newest 748450 0 peter 2012-10-23 03:30:54 -0700 There are three issues right now which impact stability and reliability of the Android layout tester: http://build.webkit.org/builders/Chromium%20Android%20Release%20%28Tests%29 1) The devices need to be rooted. Going to root is done in _setup_test, but this doesn't seem to have any effect. We should remove the need to be on a rooted device. 2) Apache2 sometimes failes to start because there are excess ipcs semaphores. These can be removed from the bot by running the following command, but they should be cleaned up in a normal way. ipcs -s | grep chrome-bot | perl -e 'while (<STDIN>) { @a=split(/\s+/); print `ipcrm sem $a[1]`}' 3) The test runner, right now, seems to be unable to detect that DRT is done. It waits for more output while nothing else will follow. http://build.webkit.org/builders/Chromium%20Android%20Release%20%28Tests%29/builds/1783/steps/layout-test/logs/stdio As an aside, the error messages shared by the layout test runner are highly unclear (plain python errors). 870898 1 peter 2013-04-08 11:02:53 -0700 Resolving as WontFix given that Chromium moved to Blink.