Searched refs:fails (Results 1 – 23 of 23) sorted by relevance
| /system/apex/tests/testdata/ |
| D | trigger_watchdog.rc | 26 # Simulate a situation when userspace reboot fails to remount userdata. Since triggers in
33 # Simulate a situation when userspace reboot fails during a shutdown sequence. This is a very crude
|
| /system/libhidl/transport/memory/1.0/ |
| D | IMapper.hal | 26 * This will be null if mapping fails.
|
| /system/tools/hidl/hidl2aidl/test/1.0/ |
| D | IFoo.hal | 26 // This case fails since string cannot be an out param in aidl.
|
| /system/sepolicy/private/ |
| D | derive_classpath.te | 15 # b/183079517 fails on gphone targets otherwise
|
| D | system_server.te | 81 # system_server. It fails to be loaded when the jar is used as a shared library, which is expected.
|
| D | domain.te | 1473 # directory write check fails and so these are never attempted.
|
| /system/extras/cppreopts/ |
| D | fstab.postinstall | 16 # Tries to mount system_other as a logical partition. If that fails, then
|
| /system/core/libprocessgroup/profiles/ |
| D | cgroups.proto | 34 // Booleans default to false when not specified. File reconstruction fails
|
| /system/apex/proto/ |
| D | session_state.proto | 62 // Populated with error details when session fails to activate
|
| /system/testing/gtest_extras/gtest_isolated/ |
| D | Isolate.cpp | 700 size_t fails = 0; in WriteXmlResults() member
723 info->fails++; in WriteXmlResults()
730 suite_entry.suite_name.c_str(), suite_entry.tests.size(), suite_entry.fails); in WriteXmlResults()
|
| /system/extras/libatrace_rust/ |
| D | README.md | 67 // Initialize the subscriber, panic if it fails.
|
| /system/sepolicy/microdroid/system/private/ |
| D | microdroid_manager.te | 108 # Allow microdroid_manager to shutdown the device when verification fails
|
| /system/core/rootdir/ |
| D | init.usb.rc | 40 # USB manager fails to set a standard configuration
|
| /system/update_engine/ |
| D | README.md | 23 * If the update fails to apply, the user is not affected. The user will
26 * If the update applies correctly but fails to boot, the system will rollback
165 and if it fails to continue the update or crashes in the middle, it will
168 * If it fails to apply a delta payload (due to bit changes on the active
|
| /system/libziparchive/cli-tests/ |
| D | unzip.test | 99 # directories, so this fails.
|
| /system/chre/platform/shared/idl/ |
| D | host_messages.fbs | 214 /// If any fragment of a load request fails, the entire load request for
|
| /system/extras/simpleperf/doc/ |
| D | README.md | 202 instructions, and fails to unwind them. This usually doesn't matter in a frame graph. But in a
|
| /system/core/fastboot/fuzzy_fastboot/ |
| D | README.md | 299 Whenever a test fails, it will print out to the console the reason for failure
|
| /system/core/init/ |
| D | README.md | 651 > * `Require`: encrypt directory, abort boot process if encryption fails
652 > * `Attempt`: try to set an encryption policy, but continue if it fails
|
| /system/apex/docs/ |
| D | README.md | 639 of the postinstall OTA routine. If decompression fails, `apexd` will fallback to
|
| /system/chre/pal/doc/ |
| D | Doxyfile | 593 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
|
| /system/chre/chre_api/doc/ |
| D | Doxyfile | 593 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
|
| /system/media/audio_utils/ |
| D | Doxyfile | 640 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
|