Home
last modified time | relevance | path

Searched refs:generated (Results 1 – 25 of 55) sorted by relevance

123

/tools/tradefederation/core/
D.gitignore5 # Intellij generated files
10 # python coverage generated files.
/tools/tradefederation/core/javatests/res/testtype/
Dpython_output4.txt11 Pull a randomly generated directory of files from the device. ... ok
15 Pull a randomly generated file from specified device. ... ok
17 Pull a randomly generated directory of files from the device. ... ok
28 Push a randomly generated file to specified device. ... ok
30 Push a randomly generated directory of files to the device. ... ok
48 Pull a randomly generated directory of files from the device. ... ok
52 Pull a randomly generated file from specified device. ... ok
54 Pull a randomly generated directory of files from the device. ... ok
65 Push a randomly generated file to specified device. ... ok
67 Push a randomly generated directory of files to the device. ... ok
[all …]
/tools/netsim/src/
DCMakeLists.txt30 # Make sure we have the cxx files generated before we build them.
53 # Make sure we have the cxx files generated before we build them.
95 # Make sure we have the cxx files generated before we build them.
/tools/netsim/testing/netsim-grpc/src/netsim_grpc/proto/
DREADME.md1 This directory contains the proto-generated python files for netsim frontend gRPC service.
/tools/asuite/
D.gitignore16 # Intellij generated files
/tools/asuite/atest/unittest_data/cache_root/
DREADME.md1 Theses cache files are generated by atest. To regenerate them:
/tools/carrier_settings/bin/
DREADME.md14 2. Copy the generated binary to this directory:
/tools/metalava/metalava/src/testdata/prebuilts-sdk-test/
DREADME.md3 The directory tree and generated jar files will be build as part of the metalava
/tools/asuite/asuite_plugin/
DREADME.md9 The artifact will be generated at build/libs/asuite_plugin-1.0.jar.
/tools/metalava/metalava/src/test/java/com/android/tools/metalava/stub/
DStubsTest.kt1501 … fun `From-text stubs can be generated from signature files with conflicting class definitions`() { in From-text stubs can be generated from signature files with conflicting class definitions()
1617 …fun `Compilable stubs are not generated when inheriting class exists in jar passed via classpath`(… in Compilable stubs are not generated when inheriting class exists in jar passed via classpath()
/tools/test/connectivity/acts/framework/acts/controllers/buds_lib/dev_utils/proto/google/protobuf/
Ddescriptor.proto235 // just annotations which may cause code to be generated slightly differently
266 // Sets the Java package where classes generated from this .proto will be
284 // generated to contain the file's getDescriptor() method as well as any
295 // the generated methods compute their results based on field values rather
318 // Sets the Go package where structs generated from this .proto will be
327 // Should generic services be generated in each language? "Generic" services
328 // are not specific to any particular RPC system. They are generated by the
349 // only to generated classes for C++.
392 // Whether the message is an automatically generated map entry type for the
455 // This option does not affect the public interface of any generated code;
[all …]
/tools/test/mobly_extensions/tools/results_uploader/
DCHANGELOG.md14 * The generated link now points directly to the "Tests" dashboard.
DREADME.md6 It uploads test-generated files to Google Cloud Storage, and presents the
/tools/treble/build/
DREADME.md70 Contains all files generated during a build. This includes target files
/tools/treble/build/treble_build/
DREADME.md33 By default a report is generated for all above commands, extra targets can
/tools/test/connectivity/acts/framework/acts/controllers/buds_lib/dev_utils/proto/
Dplugin.proto90 // Represents a single generated file.
99 // and allows the generated text to be streamed back to protoc so that large
118 // The double-@ is intended to make it unlikely that the generated code
Dnanopb.proto49 // Add 'packed' attribute to generated structs.
/tools/netsim/rust/cli/
Dnetsim-cli.md41 …ICE_NAME\]: Optional name of the device to create. A default name will be generated if not supplied
42 …May only be specified if DEVICE_NAME is specified. A default name will be generated if not supplied
/tools/metalava/metalava/src/test/java/com/android/tools/metalava/lint/
DFlaggedApiLintTest.kt430 fun `Require @FlaggedApi to reference generated fields`() { in Require @FlaggedApi to reference generated fields()
/tools/trebuchet/
DREADME.md3 Trebuchet is a Kotlin library for parsing and analyzing Android trace files generated by the `atrac…
/tools/test/connectivity/acts_tests/tests/google/tel/config/
DREADME.md6 …le provides key/value pairs mapping ICCIDs to MSISDNs. This file can be generated and amended by t…
/tools/metalava/
DREADME.md192 generated the signature files and generated the stubs had diverged, so there
298 just one example, the code which generated documentation for typedef constants
307 this was generated manually via the development/tools/extract code. This also
311 * Support for extracting API levels (api-versions.xml). This was generated by
316 doclava, which sometimes generated incorrect results. Metalava uses the
474 Doclava1 was integrated with javadoc directly, so the way it generated metadata
DAPI-LINT.md61 behalf to a generated file in the out/ folder, and if there's a failure metalava
189 (This is generated when metalava is invoked with both --verbose and --update-baseline.)
/tools/netsim/rust/
DCMakeLists.txt35 # Make sure we have the rust packets generated before we build them.
/tools/netsim/cmake/
Dnetsim_dependencies.cmake124 # We need the auto generated header for some components, so let's set the
125 # ANDROID_HW_CONFIG_H variable to point to the generated header. Those that need

123