docs/android_test_instructions.md - Issue 2760383003: Roll Android SDK to N-MR1

Side by Side Diff: docs/android_test_instructions.md

Issue 2760383003: Roll Android SDK to N-MR1 (Closed)

Patch Set: Rebase again Created 3 years, 8 months 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 140 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
151 builder.	151 builder.

152	152

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

154	154

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

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

157 with the following commands:	157 with the following commands:

158	158

159 ```shell	159 ```shell

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

161 resize2fs android_emulator_sdk/sdk/system-images/android-24/x86/userdata.img 1G	161 resize2fs android_emulator_sdk/sdk/system-images/android-25/x86/userdata.img 1G

162	162

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

164 # things e2fsprogs does.	164 # things e2fsprogs does.

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

166 ```	166 ```

167	167

168 ## Symbolizing Crashes	168 ## Symbolizing Crashes

169	169

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

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

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

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

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

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

(...skipping 130 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
306	306

307 See [Layout Tests](testing/layout_tests.md).	307 See [Layout Tests](testing/layout_tests.md).

308	308

309 ## Running GPU tests	309 ## Running GPU tests

310	310

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

312	312

313 See https://www.chromium.org/developers/testing/gpu-testing for details. Use	313 See https://www.chromium.org/developers/testing/gpu-testing for details. Use

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

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

OLD	NEW

« build/android/devil_chromium.json ('K') | « components/cronet/android/api/build.xml ('k') | tools/android/eclipse/.classpath » ('j') | no next file with comments »