Searched refs:configuration (Results 1 – 25 of 36) sorted by relevance
12
24 configuration. The test beds and their corresponding test files are:40 The test configuration, the `<config>` in the commands above, is stored in41 the *config* sub-directory. The configuration simply uses all connected45 The only provided configuration is *wifi_rtt.json*.47 The configuration defines the following keys to configure the test:51 configuration of the AP used in the test.
43 // The suite names that the configuration belong to.45 // A set of metadata representing some configuration attributes47 // Whether the configuration is shardable or not.49 // Whether the configuration is strict shardable or not.51 // Whether we are currently running the configuration in sandbox mode or not.
31 // name can be found in the Tradefed configuration xml of the test.35 // The configuration description associated with the test configuration.
39 1. Read configuration files97 - -c acts_confidence_test_config: is the flag and name of the configuration file106 contents of a sample configuration file:109 { "_description": "This is an example skeleton test configuration file.",125 standard a ':'-delimited format. Explicit keys in a configuration file will131 and are created based on the provided configuration file.
27 import com.android.tools.metalava.model.configuration in <lambda>()105 val severity = configuration.getSeverity(id) in hasErrors()120 val severity = configuration.getSeverity(id) in report()135 val severity = configuration.getSeverity(id) in report()180 val severity = configuration.getSeverity(id) in isSuppressed()
34 import com.android.tools.metalava.model.configuration887 … if (reporter.report(issue, item, message) && configuration.getSeverity(issue) == Severity.ERROR) { in report()907 val previousConfiguration = configuration in checkCompatibility()913 configuration = issueConfiguration in checkCompatibility()916 configuration = previousConfiguration in checkCompatibility()
25 import com.android.tools.metalava.model.configuration in <lambda>()91 … if (options.baselineErrorsOnly && configuration.getSeverity(issue) != Severity.ERROR) { in <lambda>()
12 * create_avd.sh creates a minimal AVD configuration from an AVD image.14 * patch_avd.sh changes an AVD configuration for bigger RAM, heap & data disk. So it can perform pro…15 * patch_all_avds.sh changes all AVD configuration for more RAM & heap. So it can perform properly.
100 // MMS configuration.194 // Name of the client for which the configuration items need to198 // Binary blob containing the configuration. The format199 // of the configuration depends on the specific client.
1 <configuration description="Common preparer">2 </configuration>
1 <configuration description="VTS Serving Plan for Staging(new) tests">2 </configuration>
1 <configuration description="VTS Serving Plan for Staging(new) tests">3 </configuration>
1 <configuration description="VTS Serving Plan for Staging(new) tests">4 </configuration>
1 <configuration description="Config for CTS Jank test cases">15 </configuration>
1 <configuration description="Config for CTS Jank test cases">18 </configuration>
1 <configuration description="Config for CTS Jank test cases">19 </configuration>
1 <configuration description="Config for VTS target parsing">30 </configuration>
33 // SSH key configuration37 // Storage configuration55 // * They are stored as plain text in the configuration file so they are
49 // Internal configuration
296 configuartion||configuration297 configuratoin||configuration298 configuraton||configuration299 configuretion||configuration300 configutation||configuration
185 public void setConfiguration(IConfiguration configuration) { in setConfiguration() argument186 mConfiguration = configuration; in setConfiguration()
60 var configuration = defaultConfiguration variable
14 **Debug in IntelliJ:** Edit configurations -> use `+` to add a Gradle configuration -> fill
5 # All configuration options are described in
16 and source tree. This is solved by manually fine-tuning a tool configuration XML