Searched full:telemetry (Results 1 – 25 of 456) sorted by relevance
12345678910>>...19
| /external/autotest/server/cros/ |
| D | telemetry_runner.py | 26 TELEMETRY_RUN_TESTS_SCRIPT = 'tools/telemetry/run_tests' 30 DUT_CHROME_ROOT = '/usr/local/telemetry/src' 41 # A list of telemetry tests that cannot run on dut. 49 """Class to represent the results of a telemetry run. 51 This class represents the results of a telemetry run, whether it ran 59 @param stdout: Stdout of the telemetry run. 60 @param stderr: Stderr of the telemetry run. 75 The TelemetryRunner class, today, has various ways to execute the telemetry 98 """Class responsible for telemetry for a given build. 100 This class will extract and install telemetry environment and is [all …]
|
| D | telemetry_setup.py | 5 """A class that sets up the environment for telemetry testing.""" 49 """Class that sets up the environment for telemetry testing.""" 52 _BASE_DIR_PATH = '/tmp/telemetry-workdir' 60 # Names of the telemetry dependency tarballs. 75 hostname: The host for which telemetry environment should be setup. This 77 build: The build for which telemetry environment should be setup. It is 83 self._setup_dir_path = tempfile.mkdtemp(prefix='telemetry-setupdir_') 89 """Sets up the environment for telemetry testing. 91 This method downloads the telemetry dependency tarballs and extracts 95 Path to the src directory where the telemetry dependencies have been [all …]
|
| /external/autotest/client/common_lib/cros/manual/ |
| D | meet_helper.py | 17 Restart chrome and wait for telemetry commands to be ready. 18 @param handle: CfM telemetry remote facade, 30 errmsg = 'Fail to run telemetry api restart_chrome_for_cfm.' 38 @param handle: CfM telemetry remote facade, 63 errmsg = 'Fail to run telemetry api to join meeting.' 70 @param handle: CfM telemetry remote facade, 83 errmsg = 'Fail to run telemetry api to leave meeting.' 92 @param handle: CfM telemetry remote facade, 106 errmsg = 'Fail to run telemetry api to mute/unmute camera.' 114 @param handle: CfM telemetry remote facade, [all …]
|
| /external/chromium-trace/catapult/devil/devil/ |
| D | devil_dependencies.json | 6 "cloud_storage_bucket": "chromium-telemetry", 16 "cloud_storage_bucket": "chromium-telemetry", 26 "cloud_storage_bucket": "chromium-telemetry", 36 "cloud_storage_bucket": "chromium-telemetry", 46 "cloud_storage_bucket": "chromium-telemetry", 56 "cloud_storage_bucket": "chromium-telemetry", 66 "cloud_storage_bucket": "chromium-telemetry", 80 "cloud_storage_bucket": "chromium-telemetry", 90 "cloud_storage_bucket": "chromium-telemetry", 112 "cloud_storage_bucket": "chromium-telemetry", [all …]
|
| /external/kernel-headers/original/uapi/linux/ |
| D | pfrut.h | 175 * struct pfrt_log_data_info - Log Data from telemetry service. 178 * @chunk1_addr_lo: Low 32bit physical address of the telemetry data chunk1 180 * @chunk1_addr_hi: High 32bit physical address of the telemetry data chunk1 182 * @chunk2_addr_lo: Low 32bit physical address of the telemetry data chunk2 184 * @chunk2_addr_hi: High 32bit physical address of the telemetry data chunk2 187 * @chunk1_size: Data size in bytes of the telemetry data chunk1 buffer. 188 * @chunk2_size: Data size in bytes of the telemetry data chunk2 buffer. 189 * @rollover_cnt: Number of times telemetry data buffer is overwritten 190 * since telemetry buffer reset. 191 * @reset_cnt: Number of times telemetry services resets that results in [all …]
|
| /external/autotest/server/site_tests/telemetry_AFDOGenerate/ |
| D | telemetry_AFDOGenerate.py | 12 Given that the telemetry benchmarks are quite unstable on ChromeOS at 14 executed outside of the telemetry framework. It is not the same as 15 executing the benchmarks under telemetry because there is no telemetry 77 DUT_CHROME_RESULTS_DIR = '/usr/local/telemetry/src/tools/perf' 100 # based on the "superhero" list and other telemetry benchmarks. Goal is 145 Run one or more telemetry benchmarks under the "perf" monitoring 219 """Run a set of telemetry benchmarks. 236 # Remove write protection on host, as now telemetry code will 300 # Use local copy of telemetry instead of using the dev server copy. 304 # Try to use the minimal support from Telemetry. The Telemetry [all …]
|
| /external/perfetto/src/trace_processor/metrics/sql/experimental/ |
| D | reported_by_page.sql | 26 AND (name = 'navigationStart' OR name GLOB 'telemetry:reported_by_page:*') 41 (p.name GLOB 'telemetry:reported_by_page:*' 42 AND p.name NOT GLOB 'telemetry:reported_by_page:benchmark*' 45 OR (p.name = 'telemetry:reported_by_page:benchmark_end' 46 AND name = 'telemetry:reported_by_page:benchmark_begin') 59 WHERE name = 'telemetry:reported_by_page:viewable'), 62 WHERE name = 'telemetry:reported_by_page:interactive'), 65 WHERE name = 'telemetry:reported_by_page:benchmark_end')
|
| /external/autotest/server/site_tests/telemetry_ScrollingActionTests/ |
| D | telemetry_ScrollingActionTests.py | 32 """Run the telemetry scrolling action tests.""" 37 """Run the telemetry scrolling action tests. 39 @param host: host we are running telemetry on. 42 host) as telemetry: 43 result = telemetry.run_telemetry_test('ScrollingActionTest') 45 'Telemetry completed with a status of: %s with '
|
| /external/tensorflow/tensorflow/lite/experimental/telemetry/ |
| D | profiler.h | 22 #include "tensorflow/lite/experimental/telemetry/telemetry_settings.h" 23 #include "tensorflow/lite/experimental/telemetry/telemetry_status.h" 27 // Telemetry profiler interface. 28 // When installed, the telemetry profilers accepts profiler events exported from 35 // General Telemetry events. 37 // Reports a telemetry event with status. 45 // Reports an op telemetry event with status. 52 // Telemetry ReportSettings events.
|
| /external/autotest/server/site_tests/telemetry_Benchmarks/ |
| D | telemetry_Benchmarks.py | 34 """Run a telemetry benchmark.""" 39 """Run a telemetry benchmark. 41 @param host: hostname(ip address) to run the telemetry benchmark on. 42 @param benchmark: telemetry benchmark test to run. 56 host, local, **optional) as telemetry: 63 telemetry.run_telemetry_benchmark(benchmark, perf_value_writer,
|
| /external/autotest/metadata/tests/ |
| D | telemetry.star | 13 'telemetry/AFDOGenerate', 18 'telemetry/AFDOGenerateClient', 23 'telemetry/Crosperf', 28 'telemetry/Sanity', 33 'telemetry/ScrollingActionTests',
|
| /external/chromium-trace/catapult/common/py_trace_event/py_trace_event/trace_event_impl/ |
| D | log.py | 46 # If a ClockSnapshot message with these default values is emitted, Telemetry 48 # TELEMETRY and BOOTTIME timestamps are the same. This allows the old-style 50 # If we want to actually synchronize Telemetry with other trace producers 53 # trace processor will translate both Chrome's and telemetry's timestamps 351 clock_domain="TELEMETRY", 369 # TODO(crbug.com/948633): For right now, we use "TELEMETRY" as the 370 # clock domain to guarantee that Telemetry is given its own clock 371 # domain. Telemetry isn't really a clock domain, though: it's a 373 # WIN_QPC. However, there's a chance that a Telemetry controller 379 # tuple. Giving Telemetry its own clock domain is a work-around [all …]
|
| /external/google-cloud-java/java-monitoring/proto-google-cloud-monitoring-v3/src/main/java/com/google/monitoring/v3/ |
| D | BasicSliOrBuilder.java | 30 * OPTIONAL: The set of RPCs to which this SLI is relevant. Telemetry from 46 * OPTIONAL: The set of RPCs to which this SLI is relevant. Telemetry from 62 * OPTIONAL: The set of RPCs to which this SLI is relevant. Telemetry from 79 * OPTIONAL: The set of RPCs to which this SLI is relevant. Telemetry from 97 * OPTIONAL: The set of locations to which this SLI is relevant. Telemetry 113 * OPTIONAL: The set of locations to which this SLI is relevant. Telemetry 129 * OPTIONAL: The set of locations to which this SLI is relevant. Telemetry 146 * OPTIONAL: The set of locations to which this SLI is relevant. Telemetry 164 * OPTIONAL: The set of API versions to which this SLI is relevant. Telemetry 180 * OPTIONAL: The set of API versions to which this SLI is relevant. Telemetry [all …]
|
| D | ServiceOrBuilder.java | 299 * Configuration for how to query telemetry on a Service. 302 * <code>.google.monitoring.v3.Service.Telemetry telemetry = 13;</code> 304 * @return Whether the telemetry field is set. 311 * Configuration for how to query telemetry on a Service. 314 * <code>.google.monitoring.v3.Service.Telemetry telemetry = 13;</code> 316 * @return The telemetry. 318 com.google.monitoring.v3.Service.Telemetry getTelemetry(); in getTelemetry() 323 * Configuration for how to query telemetry on a Service. 326 * <code>.google.monitoring.v3.Service.Telemetry telemetry = 13;</code>
|
| /external/toolchain-utils/crosperf/experiment_files/ |
| D | telemetry-without-autotest.exp | 1 # This example experiment file shows how to run a Telemetry test 3 # script. You need to supply both the name of the Telemetry test and 17 # Replace "page_cycler_dhtml" below with the name of the Telemetry test 20 # N.B. The key to running telemetry without autotest is the 'suite' field. 23 suite: telemetry
|
| /external/google-cloud-java/java-iot/proto-google-cloud-iot-v1/src/main/java/com/google/cloud/iot/v1/ |
| D | DeviceRegistryOrBuilder.java | 82 * The configuration for notification of telemetry events received from the 83 * device. All telemetry events that were successfully published by the 87 * device telemetry event using MQTT without specifying a Cloud Pub/Sub topic 101 * The configuration for notification of telemetry events received from the 102 * device. All telemetry events that were successfully published by the 106 * device telemetry event using MQTT without specifying a Cloud Pub/Sub topic 120 * The configuration for notification of telemetry events received from the 121 * device. All telemetry events that were successfully published by the 125 * device telemetry event using MQTT without specifying a Cloud Pub/Sub topic 139 * The configuration for notification of telemetry events received from the [all …]
|
| D | DeviceRegistry.java | 186 * The configuration for notification of telemetry events received from the 187 * device. All telemetry events that were successfully published by the 191 * device telemetry event using MQTT without specifying a Cloud Pub/Sub topic 209 * The configuration for notification of telemetry events received from the 210 * device. All telemetry events that were successfully published by the 214 * device telemetry event using MQTT without specifying a Cloud Pub/Sub topic 232 * The configuration for notification of telemetry events received from the 233 * device. All telemetry events that were successfully published by the 237 * device telemetry event using MQTT without specifying a Cloud Pub/Sub topic 254 * The configuration for notification of telemetry events received from the [all …]
|
| /external/google-cloud-java/java-service-control/grpc-google-cloud-service-control-v2/src/main/java/com/google/api/servicecontrol/v2/ |
| D | ServiceControllerGrpc.java | 27 * This API provides admission control and telemetry reporting for services 179 * This API provides admission control and telemetry reporting for services 222 * This method provides telemetry reporting for services that are integrated 227 * [Telemetry 228 * Reporting](https://cloud.google.com/service-infrastructure/docs/telemetry-reporting). 229 * NOTE: The telemetry reporting has a hard limit of 1000 operations and 1MB 253 * This API provides admission control and telemetry reporting for services 274 * This API provides admission control and telemetry reporting for services 328 * This method provides telemetry reporting for services that are integrated 333 * [Telemetry [all …]
|
| /external/autotest/server/cros/power/ |
| D | power_telemetry_logger.py | 6 """Helper class for power measurement with telemetry devices.""" 70 """A helper class for power autotests requiring telemetry devices. 72 Telemetry: external pieces of hardware which help with measuring power 74 telemetry.core, which is a required library / dependency for autotests 75 involving Chrome and / or ARC. Examples of power telemetry devices include 78 This logger class detects telemetry devices connected to the DUT. It will 79 then start and stop the measurement, trim the excessive power telemetry 91 power telemetry devices. 106 """Start power telemetry devices.""" 112 """Start power telemetry devices.""" [all …]
|
| /external/autotest/client/cros/power/ |
| D | power_telemetry_utils.py | 6 """Helper class for power autotests requiring telemetry devices.""" 124 """Mark the start of power telemetry measurement. 128 telemetry data should start. PowerTelemetryLogger will trim off excess data 129 before this point. If not used, power telemetry data will start right before 140 """Mark the end of power telemetry measurement. 144 telemetry data should end. PowerTelemetryLogger will trim off excess data 145 after this point. If not used, power telemetry data will end right after the
|
| /external/autotest/server/site_tests/chromium_Telemetry/ |
| D | chromium_Telemetry.py | 19 """Run a telemetry benchmark on browser infra built Chrome.""" 29 # The path that telemetry backend can find chrome. 65 """Run a telemetry benchmark.""" 74 is_lacros=True) as telemetry: 76 telemetry.run_telemetry_benchmark(self.benchmark,
|
| /external/autotest/client/common_lib/cros/ |
| D | enrollment.py | 22 @param browser: telemetry browser object. 34 @param browser: telemetry browser object. 52 @param browser: telemetry browser object. 74 @param browser: telemetry browser object. 83 @param browser: telemetry browser object.
|
| /external/skia/tools/skp/page_sets/ |
| D | skia_linkedin_desktop.py | 10 from telemetry import story 11 from telemetry.page import page as page_module 12 from telemetry.page import shared_page_state 13 from telemetry.util import wpr_modes
|
| /external/perfetto/protos/perfetto/metrics/chrome/ |
| D | reported_by_page.proto | 24 // Time from navigation start to telemetry:reported_by_page:viewable. 26 // Time from navigation start to telemetry:reported_by_page:interactive. 28 // Time from telemetry:reported_by_page:benchmark_begin to 29 // telemetry:reported_by_page:benchmark_end.
|
| /external/chromium-trace/catapult/common/py_utils/py_utils/ |
| D | chrome_binaries.json | 6 "cloud_storage_bucket": "chrome-telemetry", 30 "cloud_storage_bucket": "chrome-telemetry", 42 "cloud_storage_bucket": "chrome-telemetry", 107 "cloud_storage_bucket": "chrome-telemetry", 131 "cloud_storage_bucket": "chrome-telemetry", 143 "cloud_storage_bucket": "chrome-telemetry",
|
12345678910>>...19