| /system/tools/hidl/c2hal/test/ |
| D | build_all.py | 32 success, failure = genFiles(path, is_open_gl)
35 print("Failure: ", ", ".join(failure))
37 ratio = len(success) / (len(success) + len(failure))
50 failure = []
69 failure += [header]
71 return success, failure
|
| /system/update_engine/payload_consumer/ |
| D | fake_file_descriptor.cc | 31 for (const auto& failure : failure_ranges_) { in Read() local
34 if (failure.first <= offset_ && offset_ < failure.first + failure.second) { in Read()
38 if (failure.first > offset_) in Read()
39 first_failure = std::min(first_failure, failure.first); in Read()
|
| /system/core/init/ |
| D | subcontext.cpp | 96 auto* failure = reply->mutable_failure(); in RunCommand() local
97 failure->set_error_string(result.error().message()); in RunCommand()
98 failure->set_error_errno(result.error().code()); in RunCommand()
107 auto* failure = reply->mutable_failure(); in ExpandArgs() local
108 failure->set_error_string(expanded_arg.error().message()); in ExpandArgs()
109 failure->set_error_errno(0); in ExpandArgs()
291 auto& failure = subcontext_reply->failure(); in Execute() local
292 return ResultError(failure.error_string(), failure.error_errno()); in Execute()
315 auto& failure = subcontext_reply->failure(); in ExpandArgs() local
316 return ResultError(failure.error_string(), failure.error_errno()); in ExpandArgs()
|
| D | subcontext.proto | 38 Failure failure = 2; field
|
| /system/sepolicy/prebuilts/api/30.0/private/ |
| D | app.te | 10 # not the cause of the failure, but just a symptom that
11 # storage isn't ready. Many apps handle the failure appropriately.
|
| D | init.te | 40 # Allow the BoringSSL self test to request a reboot upon failure
|
| /system/sepolicy/private/ |
| D | app.te | 21 # not the cause of the failure, but just a symptom that
22 # storage isn't ready. Many apps handle the failure appropriately.
|
| D | init.te | 40 # Allow the BoringSSL self test to request a reboot upon failure
|
| /system/sepolicy/prebuilts/api/29.0/private/ |
| D | init.te | 33 # Allow the BoringSSL self test to request a reboot upon failure
|
| /system/core/cli-test/ |
| D | cli-test.cpp | 272 for (auto& failure : failures) { in RunTests() local
273 Print(kRed, "[ FAILED ]", " %s", failure.c_str()); in RunTests()
|
| D | README.md | 58 Anything else is considered a test failure.
66 expected to be empty, and any output will cause a test failure. (The support is
|
| /system/bt/stack/smp/ |
| D | smp_act.cc | 234 p_cb->failure = p_data->status; in smp_send_pair_fail()
237 p_cb->failure); in smp_send_pair_fail()
1089 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_proc_compare()
1616 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_peer_nonce()
1627 p_cb->failure = SMP_NUMERIC_COMPAR_FAIL; in smp_process_peer_nonce()
1640 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_peer_nonce()
1664 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_peer_nonce()
1711 p_cb->failure = SMP_DHKEY_CHK_FAIL; in smp_match_dhkey_checks()
1830 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_secure_connection_oob_data()
|
| /system/bt/doc/ |
| D | pts_guide.md | 43 - `PTS_SmpFailureCase` enables handling for various SMP failure cases.
|
| /system/libhidl/transport/token/1.0/ |
| D | ITokenManager.hal | 29 * Must return empty token on failure.
|
| /system/core/fastboot/fuzzy_fastboot/ |
| D | README.md | 184 …led and anything from the launched programs stderr is logged in the test failure. | Empty String (…
197 … a return code of 0 to signal the parsing was successful. In the case of failure, return a non-zer…
299 Whenever a test fails, it will print out to the console the reason for failure
300 and the lines and file where the error happened. At the end of each failure
319 backtrace of the underlying fastboot commands leading up the failure in this test.
327 One can easily see the reason for the failure was the test expected the device to
330 If it is still unclear why the failure is happening, the last thing to do is look
354 (i.e. with valid input), as well as the opposite. Make sure the failure tests
389 - *Saved Test Log*: Fuzzy Fastboot should be able to create a failure log for every failing test an…
|
| /system/bt/service/doc/ |
| D | IBluetoothGattClientCallback.txt | 75 * can be ignored in case of failure.
103 * can be ignored in case of failure.
|
| /system/core/logcat/ |
| D | event.logtags | 132 # libc failure logging
148 # libcore failure logging
|
| D | logcatd.rc | 13 # expect /init to report failure if property empty (default)
|
| /system/sepolicy/prebuilts/api/28.0/public/ |
| D | hal_neverallows.te | 17 # will result in CTS failure.
|
| /system/sepolicy/public/ |
| D | hal_neverallows.te | 18 # will result in CTS failure.
|
| /system/sepolicy/prebuilts/api/29.0/public/ |
| D | hal_neverallows.te | 17 # will result in CTS failure.
|
| /system/sepolicy/prebuilts/api/30.0/public/ |
| D | hal_neverallows.te | 18 # will result in CTS failure.
|
| /system/core/adb/ |
| D | OVERVIEW.TXT | 102 2. For failure, the 4-byte "FAIL" string, followed by a
104 for failure.
|
| /system/bpf/bpfloader/ |
| D | bpfloader.rc | 40 # bpfloader succeeding is critical to system health, since a failure will
|
| /system/core/fastboot/ |
| D | README.md | 40 of the response (if present) provide a textual failure message
62 b. FAIL -> display the remaining 60 bytes (if present) as a failure
78 Client: "FAILUnknown variable" getvar failure; see getvar details below
96 Client: "FAILunknown command" indicate failure
|