/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 | 98 auto* failure = reply->mutable_failure(); in RunCommand() local 99 failure->set_error_string(result.error().message()); in RunCommand() 100 failure->set_error_errno(result.error().code()); in RunCommand() 109 auto* failure = reply->mutable_failure(); in ExpandArgs() local 110 failure->set_error_string(expanded_arg.error().message()); in ExpandArgs() 111 failure->set_error_errno(0); in ExpandArgs() 307 auto& failure = subcontext_reply->failure(); in Execute() local 308 return ResultError<>(failure.error_string(), failure.error_errno()); in Execute() 331 auto& failure = subcontext_reply->failure(); in ExpandArgs() local 332 return ResultError<>(failure.error_string(), failure.error_errno()); in ExpandArgs()
|
D | subcontext.proto | 38 Failure failure = 2; field
|
/system/sepolicy/prebuilts/api/34.0/private/ |
D | mm_events.te | 9 # to arm mm_events on failure.
|
D | shared_relro.te | 14 # StrictMode may attempt to find this service, failure is harmless.
|
/system/sepolicy/prebuilts/api/32.0/private/ |
D | mm_events.te | 9 # to arm mm_events on failure.
|
D | shared_relro.te | 14 # StrictMode may attempt to find this service, failure is harmless.
|
D | app.te | 28 # not the cause of the failure, but just a symptom that 29 # storage isn't ready. Many apps handle the failure appropriately.
|
/system/sepolicy/private/ |
D | mm_events.te | 9 # to arm mm_events on failure.
|
D | shared_relro.te | 14 # StrictMode may attempt to find this service, failure is harmless.
|
/system/sepolicy/prebuilts/api/33.0/private/ |
D | mm_events.te | 9 # to arm mm_events on failure.
|
D | shared_relro.te | 14 # StrictMode may attempt to find this service, failure is harmless.
|
/system/sepolicy/prebuilts/api/31.0/private/ |
D | mm_events.te | 9 # to arm mm_events on failure.
|
D | shared_relro.te | 14 # StrictMode may attempt to find this service, failure is harmless.
|
D | app.te | 27 # 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/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.
|
/system/chre/apps/test/common/proto/ |
D | permission_test.proto | 17 // use this message to report a failure.
|
D | ping_test.proto | 19 // use this message to report a failure.
|
D | chre_stress_test.proto | 18 // message to report a failure.
|
/system/chre/core/ |
D | chre_metrics.proto | 64 // The reason for the failure. 106 // The PAL this failure event is for. 109 // The type of failure observed. 132 // An unspecified failure occurred.
|
/system/core/fs_mgr/libsnapshot/android/snapshot/ |
D | snapshot.proto | 150 // To understand the source of each failure, read snapshot.cpp. To handle new 151 // sources of failure, avoid reusing an existing code; add a new code instead. 198 // Merge failure code, filled if state == MergeFailed. 238 // Merge failure code, filled if the merge failed at any time (regardless
|
/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 | 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/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…
|