Home
last modified time | relevance | path

Searched refs:failure (Results 1 – 25 of 113) sorted by relevance

12345

/system/tools/hidl/c2hal/test/
Dbuild_all.py32 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/
Dfake_file_descriptor.cc31 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/
Dsubcontext.cpp97 auto* failure = reply->mutable_failure(); in RunCommand() local
98 failure->set_error_string(result.error().message()); in RunCommand()
99 failure->set_error_errno(result.error().code()); in RunCommand()
108 auto* failure = reply->mutable_failure(); in ExpandArgs() local
109 failure->set_error_string(expanded_arg.error().message()); in ExpandArgs()
110 failure->set_error_errno(0); in ExpandArgs()
298 auto& failure = subcontext_reply->failure(); in Execute() local
299 return ResultError(failure.error_string(), failure.error_errno()); in Execute()
322 auto& failure = subcontext_reply->failure(); in ExpandArgs() local
323 return ResultError(failure.error_string(), failure.error_errno()); in ExpandArgs()
Dsubcontext.proto38 Failure failure = 2; field
/system/sepolicy/private/
Dmm_events.te9 # to arm mm_events on failure.
Dshared_relro.te14 # StrictMode may attempt to find this service, failure is harmless.
Dapp.te27 # not the cause of the failure, but just a symptom that
28 # storage isn't ready. Many apps handle the failure appropriately.
/system/sepolicy/prebuilts/api/31.0/private/
Dmm_events.te9 # to arm mm_events on failure.
Dshared_relro.te14 # StrictMode may attempt to find this service, failure is harmless.
Dapp.te27 # not the cause of the failure, but just a symptom that
28 # storage isn't ready. Many apps handle the failure appropriately.
/system/iorap/src/inode2filename/
Dout_of_process_inode_resolver.cc68 std::ios_base::failure IosBaseFailureWithErrno(const char* message) { in IosBaseFailureWithErrno()
70 return std::ios_base::failure(message, ec); in IosBaseFailureWithErrno()
342 rxcpp::util::make_error_ptr(std::ios_base::failure(error_msg))); in EmitFromCommandWithArgv()
360 rxcpp::util::make_error_ptr(std::ios_base::failure(ss.str()))); in EmitFromCommandWithArgv()
Ddata_source.cc111 std::ios_base::failure("Could not open specified text cache filename"))); in EmitInodes()
/system/sepolicy/prebuilts/api/30.0/private/
Dapp.te10 # not the cause of the failure, but just a symptom that
11 # storage isn't ready. Many apps handle the failure appropriately.
/system/chre/apps/test/common/proto/
Dpermission_test.proto17 // use this message to report a failure.
Dping_test.proto19 // use this message to report a failure.
Dchre_stress_test.proto18 // message to report a failure.
/system/core/fs_mgr/libsnapshot/android/snapshot/
Dsnapshot.proto144 // To understand the source of each failure, read snapshot.cpp. To handle new
145 // sources of failure, avoid reusing an existing code; add a new code instead.
192 // Merge failure code, filled if state == MergeFailed.
226 // Merge failure code, filled if state == MergeFailed.
/system/sepolicy/prebuilts/api/29.0/private/
Dinit.te33 # Allow the BoringSSL self test to request a reboot upon failure
/system/core/cli-test/
DREADME.md58 Anything else is considered a test failure.
66 expected to be empty, and any output will cause a test failure. (The support is
Dcli-test.cpp279 for (auto& failure : failures) { in RunTests() local
280 Print(kRed, "[ FAILED ]", " %s", failure.c_str()); in RunTests()
/system/bt/doc/
Dpts_guide.md43 - `PTS_SmpFailureCase` enables handling for various SMP failure cases.
/system/bt/stack/smp/
Dsmp_act.cc245 p_cb->failure = p_data->status; in smp_send_pair_fail()
248 p_cb->failure); in smp_send_pair_fail()
1111 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_proc_compare()
1667 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_peer_nonce()
1678 p_cb->failure = SMP_NUMERIC_COMPAR_FAIL; in smp_process_peer_nonce()
1691 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_peer_nonce()
1725 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_peer_nonce()
1772 p_cb->failure = SMP_DHKEY_CHK_FAIL; in smp_match_dhkey_checks()
1891 p_cb->failure = SMP_CONFIRM_VALUE_ERR; in smp_process_secure_connection_oob_data()
/system/libhidl/transport/token/1.0/
DITokenManager.hal29 * Must return empty token on failure.
/system/bt/service/doc/
DIBluetoothGattClientCallback.txt75 * can be ignored in case of failure.
103 * can be ignored in case of failure.
/system/core/fastboot/fuzzy_fastboot/
DREADME.md184 …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…

12345