| /test/vts/proto/ |
| D | VtsResourceControllerMessage.proto | 9 // Unless required by applicable law or agreed to in writing, software
36 // Write to a FMQ (no blocking).
38 // Write to a FMQ (with short-form blocking).
40 // Write to a FMQ (with long-form blocking).
43 // Get space available to write in FMQ.
45 // Get number of items available to read.
55 // drivers to pass queue descriptor address to identify
67 // Signal starting to read memory.
69 // Signal starting to read a particular region of memory.
73 // Signal starting to write to memory.
[all …]
|
| D | ComponentSpecificationMessage.proto | 9 // Unless required by applicable law or agreed to in writing, software
127 // for conventional HALs, to keep a data structure with one or multiple
147 // similar to TYPE_UNION, but support runtime type check.
183 // To specify an API call to an interface.
189 // HAL driver ID, if set (e.g., >0), use the given driver_id to get the
223 // the HIDL interface ID used to call an API of another nested interface
236 // used to pass the spec of a found HAL_CONVENTIONAL_SUBMODULE to the host.
266 // not a user-provided variable. used by the frameworks to tell the sub
270 // to specify a syscall number.
308 // used for a function pointer to keep its function name.
[all …]
|
| D | AndroidSystemControlMessage.proto | 9 // Unless required by applicable law or agreed to in writing, software
119 // the name of a HAL module to open.
128 // use two ints to represent major and minor versions separately.
134 // Need to add flag TREBLE_TESTING_OVERRIDE=true in environment if it is.
137 // the name of a HW Binder service to use (only needed for HIDL HAL).
152 // for specifying requests to FMQ driver
154 // for specifying requests to hidl_memory driver
156 // for specifying requests to hidl_handle driver
194 // callback id for the message sent to the TCP Server.
|
| D | VtsDriverControlMessage.proto | 9 // Unless required by applicable law or agreed to in writing, software
25 // To request to exit a driver.
31 // To request to load a HAL.
90 // the name of a HAL module to open.
92 // the package of a HIDL HAL to open.
97 // use two ints to represent major and minor versions separately.
103 // the name of a HW Binder service to use (only needed for HIDL HAL).
|
| /test/mlts/models/assets/asr_float/ |
| D | LICENSE | 12 disclaims all liability for damages resulting from their use to the
18 conditions that creators and other rights holders may use to share
19 original works of authorship and other material subject to copyright
25 intended for use by those authorized to give the public
26 permission to use material in ways otherwise restricted by
33 material not subject to the license. This includes other CC-
35 limitation to copyright. More considerations for licensors:
39 licenses, a licensor grants the public permission to use the
42 example, because of any applicable exception or limitation to
45 other rights that a licensor has authority to grant. Use of
[all …]
|
| /test/vti/dashboard/ |
| D | README.md | 9 ### Steps to run locally:
40 Steps to Install Maven:
44 2) Move the application directory to /usr/local
68 Therefore move the extracted folder to this location: /usr/local/share/google/
70 Otherwise, to have a custom location, specify the location of
85 ## To deploy to Google App Engine
95 The next commands show how to do it.
108 So we need to put some sample data into local datastore so that developers are able to continue to
117 ### How to set test data on json files for generating mock data on local dev server
119 If you want to generate some mock data for your local development, you need to set some fake data
[all …]
|
| /test/vts-testcase/nbu/src/ |
| D | README.md | 8 These tests simulate connectivity use cases critical to NBU market like
9 peer-to-peer interactions.
12 want to learn more, see its [Github page](https://github.com/google/mobly) and
16 Test (DUT) and Python test scripts running on a computer to which the DUTs are
17 connected via USB. The tests issue cmds to the agent on the device to trigger
20 The tests by default write output to `/tmp/logs`.
24 This section lists the components and steps required to create a setup to run
43 * Flash the build you want to test. The build's API level has to be `>=26`.
52 Based on the two devices' serial numbers, we need to create a config file.
75 In addition to those, we also need to install a few other tools:
[all …]
|
| /test/mlts/benchmark/ |
| D | LICENSE | 18 "control" means (i) the power, direct or indirect, to cause the
27 including but not limited to software source code, documentation
32 not limited to compiled object code, generated documentation,
33 and conversions to other media types.
37 copyright notice that is included in or attached to the work
45 separable from, or merely link (or bind by name) to the interfaces of,
50 to that Work or Derivative Works thereof, that is intentionally
51 submitted to Licensor for inclusion in the Work by the copyright owner
52 or by an individual or Legal Entity authorized to submit on behalf of
55 to the Licensor or its representatives, including but not limited to
[all …]
|
| D | README.txt | 9 Unless required by applicable law or agreed to in writing, software
17 Test Suite). MLTS allows to evaluate NNAPI acceleration latency and accuracy
24 * Connect a target device to your workstation, make sure it's
32 presented as html page, passed to xdg-open.
36 The MLTS suite contains a series of tests to validate the behaviour of the drivers under stress or
40 By default, every test gets run on each available accelerator in isolation. It is possible to filte…
41 accelerators to test against by invoking the build_and_run_benchmark.sh script with the option
42 -f (--filter-driver) and specifying a regular expression to filter the acccelerator names with.
43 It is also possible to run additional tests without specified target accelerator to let NNAPI
49 * parallel-inference-stress: to test the behaviour of drivers with different amount of inference
[all …]
|
| /test/mlts/models/ |
| D | LICENSE | 18 "control" means (i) the power, direct or indirect, to cause the
27 including but not limited to software source code, documentation
32 not limited to compiled object code, generated documentation,
33 and conversions to other media types.
37 copyright notice that is included in or attached to the work
45 separable from, or merely link (or bind by name) to the interfaces of,
50 to that Work or Derivative Works thereof, that is intentionally
51 submitted to Licensor for inclusion in the Work by the copyright owner
52 or by an individual or Legal Entity authorized to submit on behalf of
55 to the Licensor or its representatives, including but not limited to
[all …]
|
| /test/vts/hals/light/bullhead/ |
| D | NOTICE | 7 Unless required by applicable law or agreed to in writing, software
31 "control" means (i) the power, direct or indirect, to cause the
40 including but not limited to software source code, documentation
45 not limited to compiled object code, generated documentation,
46 and conversions to other media types.
50 copyright notice that is included in or attached to the work
58 separable from, or merely link (or bind by name) to the interfaces of,
63 to that Work or Derivative Works thereof, that is intentionally
64 submitted to Licensor for inclusion in the Work by the copyright owner
65 or by an individual or Legal Entity authorized to submit on behalf of
[all …]
|
| /test/mlts/benchmark/results/ |
| D | LICENSE | 8 …to any person obtaining a copy of this software and associated documentation files (the "Software"…
|
| /test/vti/test_serving/gae/frontend/ |
| D | NOTICE | 5 Permission is hereby granted, free of charge, to any person obtaining a copy
6 of this software and associated documentation files (the "Software"), to deal
8 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 copies of the Software, and to permit persons to whom the Software is
10 furnished to do so, subject to the following conditions:
|
| /test/vts/doc/testcase_develop_manual/ |
| D | run_vts_directly.md | 5 ## Download required Python packages to local host
29 …s.testcases.<test py package path> $ANDROID_BUILD_TOP/test/vts/testcases/<path to its config file>`
40 to your config file (e.g., `VtsKernelLtpStaging.config`).
44 In order to add a new test, the following two files needed to be extended.
50 Optionally, the command used to add a new test can be also added to:
|
| /test/vts/tools/vts-tradefed/etc/ |
| D | vts10-tradefed_win.bat | 9 :: Unless required by applicable law or agreed to in writing, software
17 :: Caution: Although this script can be used to run VTS on Windows,
25 where %ADB% || (echo Unable to find %ADB% && goto:eof)
26 where %JAVA% || (echo Unable to find %JAVA% && goto:eof)
60 echo Unable to locate %TRADEFED_JAR%. Try prebuilt jar.
64 echo Unable to locate %TRADEFED_JAR%
78 if not exist "!JAR!" ( echo Unable to locate !JAR! && goto:eof )
82 :: to run in the lab.
|
| /test/vts/testcases/vts_selftest/test_framework/python_virtualenv_preparer_test/ |
| D | README.md | 8 * VtsSelfTestPythonVirtualenvPreparerTestPart0: to verify the python module (numpy) that's going to…
9 * VtsSelfTestPythonVirtualenvPreparerTestPart1: test duplicated module preparer to install a new mo…
12 The naming of `Part0`, `Part1` and `Part2` is to ensure the order of execution.
|
| /test/vti/dashboard/src/main/proto/ |
| D | TestSuiteResultMessage.proto | 9 // Unless required by applicable law or agreed to in writing, software
23 // To specify the test results which are uploaded to vts dashboard.
28 // GCS path to the corresponding result directory
59 // GCS path to the corresponding infra log file.
62 // GCS path to the repacked device[+GSI] image set.
65 // Fetch info used to fetch and flash certain builds for retry_prompt command.
|
| /test/suite_harness/tools/cts-test-metrics/ |
| D | README | 1 The parse_test_metrics.py script can be used to parse test metrics json files. Run the following
2 command to see a demo:
12 The MetricsParser class defines functions to parse a json file. The _Parse function takes a filename
13 as input, reads the json file and adds the json object to json_data. The _PrintJson function
|
| /test/vts/testcases/vts_selftest/manual_tests/ |
| D | README.txt | 1 This directory contains test cases that require to be manually run.
3 Test cases in this directory could be designed to:
9 It is up to the user's understanding and precaution before running tests
|
| /test/vts/doc/ |
| D | user_manual.md | 3 … and running VTS. Building on Windows is not supported, but it is possible to [run VTS on Windows]…
16 …to instead install these packages from a local directory during test runtime by predownloading the…
66 ### 1.5. Connect to an Android device
86 For Windows users, please build on Linux. Then copy the following zip file to Windows and extract i…
114 After Android O release, you will be able to upload that xml file to [AFPE](https://partner.android…
136 [This doc](developer_testing/kernel/ltp.md) shows how to run each LTP test case.
|
| /test/vts/doc/developer_testing/kernel/ |
| D | run_all_ltp_testcases.md | 1 # How to run all the enabled LTP tests
11 This will take from 30 minutes to 2 hours to run.
|
| /test/suite_harness/tools/cts-tradefed/ |
| D | README | 9 It works in a similar manner to the prior CTS harness, but supports some
12 - modular, flexible extensible design. cts-tradefed can be extended to
31 3. Connect the device to the host machine.
48 'run cts' to run the default CTS plan
75 Perform these steps to build and run cts-tradefed from the development
77 cd <path to android source root>
|
| /test/vts/utils/app_engine/ |
| D | setup.txt | 1 Instructions for Setup for writing data to Big table:
3 1. Make sure gcloud is installed and the project is set to the current project.
4 Follow the instructions here to install gcloud:
|
| /test/vts/tools/vts-core-tradefed/ |
| D | README | 9 It works in a similar manner to the prior VTS harness, but with much
29 3. Connect the device to the host machine.
46 'run vts' to run the default VTS plan
73 Perform these steps to build and run vts-tradefed from the development
75 cd <path to android source root>
|
| /test/mts/tools/mts-tradefed/ |
| D | README | 5 top of the Android Trade Federation test harness to test mainline modules.
29 'run mts' to run the default MTS plan
53 Perform these steps to build and run mts-tradefed from the development
55 cd <path to android source root>
|