docs/android_test_instructions.md - Issue 2442363003: Reland of Upgrade to new Android SDK.

Side by Side Diff: docs/android_test_instructions.md

Issue 2442363003: Reland of Upgrade to new Android SDK. (Closed)

Patch Set: Created 4 years, 1 month ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
1 # Android Test Instructions	1 # Android Test Instructions

2	2

3 [TOC]	3 [TOC]

4	4

5 ## Device Setup	5 ## Device Setup

6	6

7 ### Physical Device Setup	7 ### Physical Device Setup

8	8

9 #### ADB Debugging	9 #### ADB Debugging

10	10

(...skipping 134 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
145 builder.	145 builder.

146	146

147 ### INSTALL\_FAILED\_CONTAINER\_ERROR or INSTALL\_FAILED\_INSUFFICIENT\_STORAGE	147 ### INSTALL\_FAILED\_CONTAINER\_ERROR or INSTALL\_FAILED\_INSUFFICIENT\_STORAGE

148	148

149 If you see this error when the test runner is attempting to deploy the test	149 If you see this error when the test runner is attempting to deploy the test

150 binaries to the AVD emulator, you may need to resize your userdata partition	150 binaries to the AVD emulator, you may need to resize your userdata partition

151 with the following commands:	151 with the following commands:

152	152

153 ```shell	153 ```shell

154 # Resize userdata partition to be 1G	154 # Resize userdata partition to be 1G

155 resize2fs android_emulator_sdk/sdk/system-images/android-23/x86/userdata.img 1G	155 resize2fs android_emulator_sdk/sdk/system-images/android-24/x86/userdata.img 1G

156	156

157 # Set filesystem parameter to continue on errors; Android doesn't like some	157 # Set filesystem parameter to continue on errors; Android doesn't like some

158 # things e2fsprogs does.	158 # things e2fsprogs does.

159 tune2fs -e continue android_emulator_sdk/sdk/system-images/android-23/x86/userda ta.img	159 tune2fs -e continue android_emulator_sdk/sdk/system-images/android-24/x86/userda ta.img

160 ```	160 ```

161	161

162 ## Symbolizing Crashes	162 ## Symbolizing Crashes

163	163

164 Crash stacks are logged and can be viewed using adb logcat. To symbolize the	164 Crash stacks are logged and can be viewed using adb logcat. To symbolize the

165 traces, define `CHROMIUM_OUTPUT_DIR=$OUTDIR` where `$OUTDIR` is the argument you	165 traces, define `CHROMIUM_OUTPUT_DIR=$OUTDIR` where `$OUTDIR` is the argument you

166 pass to `ninja -C`, and pipe the output through	166 pass to `ninja -C`, and pipe the output through

167 `third_party/android_platform/development/scripts/stack`. If	167 `third_party/android_platform/development/scripts/stack`. If

168 `$CHROMIUM_OUTPUT_DIR` is unset, the script will search `out/Debug` and	168 `$CHROMIUM_OUTPUT_DIR` is unset, the script will search `out/Debug` and

169 `out/Release`. For example:	169 `out/Release`. For example:

(...skipping 131 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
301 See	301 See

302 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tes ts	302 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tes ts

303	303

304 ## Running GPU tests	304 ## Running GPU tests

305	305

306 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)	306 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)

307	307

308 See http://www.chromium.org/developers/testing/gpu-testing for details. Use	308 See http://www.chromium.org/developers/testing/gpu-testing for details. Use

309 `--browser=android-content-shell`. Examine the stdio from the test invocation on	309 `--browser=android-content-shell`. Examine the stdio from the test invocation on

310 the bots to see arguments to pass to `src/content/test/gpu/run_gpu_test.py`.	310 the bots to see arguments to pass to `src/content/test/gpu/run_gpu_test.py`.

OLD	NEW

« no previous file with comments | « components/cronet/tools/generate_javadoc.py ('k') | tools/android/eclipse/.classpath » ('j') | no next file with comments »