Note about symbolic linking from "out" to "out_android"

docs/android_test_instructions.md

 # Android Test Instructions
 
 Device Setup Tests are runnable on physical devices or emulators. See the
 instructions below for setting up either a physical device or an emulator.
 
 [TOC]
 
 ## Physical Device Setup **ADB Debugging**
 
 In order to allow the ADB to connect to the device, you must enable USB
@@ skipping 105 matching lines @@
 For a list of valid test types, see `test_runner.py --help`. For
 help on a specific test type, run `test_runner.py <test_type> --help`.
 
 The commands used by the buildbots are printed in the logs. Look at
 http://build.chromium.org/ to duplicate the same test command as a particular
 builder.
 
 If you build in an output directory other than "out", you may have to tell
 test\_runner.py where you place it. Say you build your android code in
 out\_android, then do `export CHROMIUM_OUT_DIR=out_android` before running the
-command below.
+command below. You have to do this even if your "out" directory is a symlink
+pointing to "out_android".
 
 ## INSTALL\_FAILED\_CONTAINER\_ERROR or INSTALL\_FAILED\_INSUFFICIENT\_STORAGE
 
 If you see this error when test\_runner.py is attempting to deploy the test
 binaries to the AVD emulator, you may need to resize your userdata partition
 with the following commands:
 
 ```shell
 # Resize userdata partition to be 1G resize2fs
 android_emulator_sdk/sdk/system-images/android-19/x86/userdata.img 1G
@@ skipping 118 matching lines @@
 See
 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tests
 
 ## Running GPU tests
 
 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)
 
 See http://www.chromium.org/developers/testing/gpu-testing for details. Use
 --browser=android-content-shell. Examine the stdio from the test invocation on
 the bots to see arguments to pass to src/content/test/gpu/run\_gpu\_test.py.