| /third_party/grpc/tools/failures/sql/ |
| D | new_failures_24h.sql | 24 reporting AS (
48 reporting.test_binary,
49 reporting.poll_strategy,
50 reporting.job_name,
51 reporting.build_id,
52 STRING(reporting.timestamp, "America/Los_Angeles") as timestamp_MTV
54 reporting
58 reporting.test_binary = calibration.test_binary
|
| /third_party/grpc/test/cpp/qps/ |
| D | report.cc | 175 // NOP - all reporting is handled by ReportQPS. in ReportQPSPerCore()
179 // NOP - all reporting is handled by ReportQPS. in ReportLatency()
183 // NOP - all reporting is handled by ReportQPS. in ReportTimes()
187 // NOP - all reporting is handled by ReportQPS. in ReportCpuUsage()
191 // NOP - all reporting is handled by ReportQPS. in ReportPollCount()
195 // NOP - all reporting is handled by ReportQPS. in ReportQueriesPerCpuSec()
215 // NOP - all reporting is handled by ReportQPS. in ReportQPSPerCore()
219 // NOP - all reporting is handled by ReportQPS. in ReportLatency()
223 // NOP - all reporting is handled by ReportQPS. in ReportTimes()
227 // NOP - all reporting is handled by ReportQPS. in ReportCpuUsage()
[all …]
|
| /third_party/skia/third_party/externals/angle2/doc/ |
| D | GPUMemoryAnalysis.md | 1 # GPU Memory Reporting and Analysis
12 ## GPU Memory Reporting
31 ANGLE supports two types of memory reporting, both of which are enabled
55 Note: At this time, GPU memory reporting has only been tested and used on Android, where the logged
60 GPU memory reporting can be combined with other forms of debugging in order to do analysis. For
65 If an application seems to be using too much GPU memory, enabling memory reporting can reveal which
|
| /third_party/cef/libcef/common/ |
| D | crash_reporting.cc | 136 // Crash reporting for subprocesses created using the zygote will be in InitCrashReporter()
146 // Used to exclude command-line flags from crash reporting.
211 // Initialize crash reporting here on macOS and Linux. Crash reporting on in PreSandboxStartup()
219 LOG(INFO) << "Crash reporting enabled for process: " in PreSandboxStartup()
225 // After platform crash reporting have been initialized, store the command in PreSandboxStartup()
226 // line for crash reporting. in PreSandboxStartup()
242 LOG(INFO) << "Crash reporting enabled for process: " << process_type; in ZygoteForked()
|
| D | crash_reporter_client.h | 22 // reporting. On Windows this is created by the
35 // the crash config file will disable crash reporting. This method should be
43 // reporting for the process. The instance is leaked.
|
| /third_party/cJSON/ |
| D | CHANGELOG.md | 34 * Fix memory leak in cJSONUtils_FindPointerFromObjectTo. Thanks @andywolk for reporting, see [#414]…
35 * Fix bug in encode_string_as_pointer. Thanks @AIChangJiang for reporting, see [#439](https://githu…
41 * Fix infinite loop in `cJSON_Minify` (potential Denial of Service). Thanks @Alanscut for reporting…
49 …sue, see [#338](https://github.com/DaveGamble/cJSON/issues/338). Big thanks @bigric3 for reporting.
50 …exist. See [#339](https://github.com/DaveGamble/cJSON/issues/339), thanks @raiden00pl for reporting
56 * Fix package config file for `libcjson`. Thanks @shiluotang for reporting [#321](https://github.co…
63 …an array, see [#315](https://github.com/DaveGamble/cJSON/issues/315). Thanks @yuweol for reporting.
77 … fails, see [#267](https://github.com/DaveGamble/cJSON/issues/267), thanks @AlfieDeng for reporting
84 …akefile, see [#252](https://github.com/DaveGamble/cJSON/issues/252), thanks @YanhaoMo for reporting
85 …Utils.h`, see [#256](https://github.com/DaveGamble/cJSON/issues/256), thanks @daschfg for reporting
[all …]
|
| /third_party/grpc/tools/failures/ |
| D | detect_new_failures.py | 142 reporting_begin=dates['reporting']['begin'],
143 reporting_end=dates['reporting']['end'])
174 calibration reporting
248 'reporting': {
271 dates['reporting']['begin'].isoformat(),
272 dates['reporting']['end'].isoformat(),
293 print('{},{},{}'.format(dates['reporting']['begin'].isoformat(),
294 dates['reporting']['end'].isoformat(),
|
| /third_party/libinput/ |
| D | README.md | 22 [reporting bugs](https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html).
37 Reporting Bugs
46 See https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html
|
| /third_party/flutter/flutter/packages/flutter_tools/lib/src/commands/ |
| D | config.dart | 14 import '../reporting/reporting.dart';
22 help: 'Enable or disable reporting anonymously tool usage statistics and crash reports.');
93 'Analytics reporting is currently ${flutterUsage.enabled ? 'enabled' : 'disabled'}.';
119 printStatus('Analytics reporting ${value ? 'enabled' : 'disabled'}.');
|
| /third_party/flutter/flutter/packages/flutter/test/foundation/ |
| D | error_reporting_test.dart | 48 test('Error reporting - pretest', () async {
55 test('Error reporting - assert with message', () async {
100 test('Error reporting - assert with long message', () async {
139 test('Error reporting - assert with no message', () async {
183 test('Error reporting - NoSuchMethodError', () async {
205 test('Error reporting - NoSuchMethodError', () async {
225 test('Error reporting - posttest', () async {
|
| /third_party/flutter/flutter/packages/flutter_tools/test/general.shard/runner/ |
| D | runner_test.dart | 13 import 'package:flutter_tools/src/reporting/reporting.dart';
46 // This flutterVersion disables crash reporting.
60 // We are checking that, even though crash reporting failed with an
|
| D | utils.dart | 8 import 'package:flutter_tools/src/reporting/reporting.dart';
|
| /third_party/boost/libs/test/doc/testing_tools/ |
| D | boost_test_universal_macro.qbk | 24 * an extended reporting capability in case of failure: not only `BOOST_TEST` reports the location o…
44 `BOOST_TEST` provides an enhanced reporting capability: additional details of the failing operands …
47 [bt_example boost_test_macro3..BOOST_TEST enhanced reporting..run-fail]
62 [h3 Uniform reporting]
|
| D | boost_test_technical_details.qbk | 12 [bt_example boost_test_macro3..BOOST_TEST reporting..run-fail]
14 It was already mentioned that the reporting is not symmetrical (see [link boost_test.testing_tools.…
15 …tatement` appearing in the `BOOST_TEST` macro. This expression allows evaluation and reporting such
|
| /third_party/boost/libs/system/doc/system/ |
| D | introduction.adoc | 33 While exceptions are the preferred {cpp} default error code reporting
35 reporting error conditions via error code arguments and/or return values rather
39 supports both error reporting by exception and by error code.
|
| D | history.adoc | 18 reporting components have received wider public scrutiny and enhancements have
21 Networking Library Proposal for TR2, demonstrating that these error reporting
|
| /third_party/ltp/testcases/open_posix_testsuite/Documentation/ |
| D | HOWTO_BugReporting | 1 This document describes the process for reporting bugs found _by_ the
8 new, important issues and reporting them in a clear, consice, and effective
15 - Code under test that is targeted* for the POSIX Test Suite reporting.
|
| /third_party/boost/libs/test/doc/prod_use/ |
| D | program_execution_monitor.qbk | 16 Yet many C++ programs, both production and test, must run in an environment where uniform reporting…
23 detection and reporting duties by providing a replacement function `main()` which calls a user-supp…
27 Uniform error reporting is particularly useful for programs running unattended under control of scr…
30 better citizen. More uniform reporting of errors isn't a benefit to some programs, particularly pro…
33 Uniform error reporting can be also useful in test environments such as the Boost
41 To facilitate uniform error reporting the __PEM__ supplies function `main()` as part if it's implem…
122 uniform error reporting. Following files constitute the __PEM__ implementation:
|
| /third_party/python/Doc/ |
| D | bugs.rst | 33 Overview of the process involved in reporting an improvement on the tracker.
54 If the problem you're reporting is not already in the bug tracker, go back to
60 sidebar to open the bug reporting form.
92 Beyond just reporting bugs that you find, you are also welcome to submit
|
| /third_party/cef/tests/gtest/teamcity/ |
| D | README.cef | 1 Name: TeamCity C++ Unit Test Reporting
8 GTest integration for reporting to TeamCity Continuous Integration Server.
|
| /third_party/flutter/flutter/packages/flutter_tools/lib/src/reporting/ |
| D | usage.dart | 5 part of reporting;
86 /// Whether analytics reporting should be supressed.
92 /// Whether analytics reporting is enabled.
95 /// Enable or disable reporting analytics.
322 ║ https://github.com/flutter/flutter/wiki/Flutter-CLI-crash-reporting ║
328 ║ reporting. ║
|
| /third_party/selinux/libselinux/man/man3/ |
| D | set_matchpathcon_flags.3 | 41 The function is also responsible for reporting any such error, and
54 error reporting to a different destination.
|
| /third_party/mesa3d/docs/ |
| D | bugs.rst | 7 Please follow these bug reporting guidelines:
15 - If you're reporting a crash, try to use your debugger (gdb) to get a
|
| /third_party/glib/gio/ |
| D | gdatainputstream.c | 322 * @error: #GError for error reporting.
349 * @error: #GError for error reporting.
393 * @error: #GError for error reporting.
437 * @error: #GError for error reporting.
485 * @error: #GError for error reporting.
533 * @error: #GError for error reporting.
581 * @error: #GError for error reporting.
728 * @error: #GError for error reporting.
814 * @error: #GError for error reporting.
900 * @error: #GError for error reporting.
[all …]
|
| /third_party/glib/gio/tests/ |
| D | gio-du.c | 59 report_progress (gboolean reporting, in report_progress() argument
67 if (!reporting) in report_progress()
68 g_printerr ("%s: warning: does not support progress reporting\n", filename); in report_progress()
|