• Home
  • Raw
  • Download

Lines Matching +full:android +full:- +full:variables

9  * Mid-execution capture is supported with the Vulkan back-end.
10 * Mid-execution capture has many unimplemented features.
24 environment variables to define a capture frame range, or use the [capture trigger
25 property][CaptureTrigger] on Android. By default the replay will be stored in the current working
34 Some simple environment variables control frame capture:
45 * Uses mid-execution capture to write "Setup" functions that starts a Context at frame `n`.
67 A good way to test out the capture is to use environment variables in conjunction with the sample
71 …E_END=4 ANGLE_CAPTURE_OUT_DIR=samples/capture_replay out/Debug/simple_texture_2d --use-angle=vulkan
89 $ autoninja -C out/Debug capture_replay_sample
93 ## Running a perf test replay (all platforms, including Android)
95 To run your capture on any platform (Windows, Linux, Android, Mac (untested)), you'll need to
103 src/tests/restricted_traces$ ls -1 desktop_test/
123 autoninja -C out/Debug angle_perftests
124 ANGLE_CAPTURE_ENABLED=0 out/Debug/angle_perftests --gtest_filter="*desktop_test*" --verbose
126 ## Capturing an Android application
128 For more comprehensive Android capture/replay documentation, see
131 In order to capture on Android, the following additional steps must be taken. These steps
139 export PACKAGE_NAME com.android.gl2jni
143 $ adb shell mkdir -p /sdcard/Android/data/$PACKAGE_NAME/angle_capture
144 $ adb shell chmod 777 /sdcard/Android/data/$PACKAGE_NAME/angle_capture
147 2. Set properties to use for environment variables
149 On Android, it is difficult to set an environment variable before starting native code.
151 and use them to prime environment variables used by the capture code.
153 As with desktop captures, Android captures can be taken from a starting frame to an
169 $ adb pull /sdcard/Android/data/$PACKAGE_NAME/angle_capture replay_files
175 By default Context ID 1 will be replayed. On Android, Context ID 2 is more typical, some apps
184 Until we have samples building for Android, the replay sample must be run on desktop.
185 We will also be plumbing replay files into perf and correctness tests which will run on Android.
187 $ autoninja -C out/Release capture_replay_sample
218 The [python script][link_to_python_script] uses the job queue pattern. We spawn n-1 independent
224 ![Point-in-time snapshot of the job queue](img/RegressionTestingArchitecture.png)
237 python3 src/tests/capture_replay_tests.py --gtest_filter=*/ES2_Vulkan --keep-temp-files --batch-cou…
240 * `--gtest_filter` to run only specific tests
241 * `--keep-temp-files` to keep the trace files
242 * `--batch-count` to set the number of tests in a (capture) batch. More tests in a batch means that
249 [CaptureTrigger]: ../src/tests/restricted_traces/README.md#trigger-the-capture