| /cts/tools/dx-tests/lib/ |
| junit.jar | |
| /cts/tools/utils/lib/ |
| junit.jar | |
| /cts/tools/vm-tests/lib/ |
| junit.jar | |
| /cts/tools/vm-tests-tf/lib/ |
| junit.jar | |
| /external/protobuf/python/ |
| mox.py | [all...] |
| /frameworks/base/docs/html/guide/topics/testing/ |
| testing_android.jd | 539 was run. You also see all the assertion failures that occurred. These include pointers to the
540 line in the test code where the failure occurred. Assertion failures also list the expected
[all...] |
| /libcore/luni/src/main/java/java/io/ |
| File.java | [all...] |
| /build/libs/host/ |
| CopyFile.c | 157 * Failures here are "soft"; they don't produce warning messages and don't
|
| /cts/tools/tradefed-host/res/report/ |
| cts_result.xsl | 398 <xsl:with-param name="header" select="'Test Failures'" />
[all...] |
| /dalvik/docs/ |
| dexopt.html | 184 Reporting of verification failures is a tricky issue. For example,
|
| /external/chromium/base/ |
| process_util_linux.cc | 626 // For security reasons, we want malloc failures to be fatal. Too much code
|
| /external/chromium/chrome/browser/chromeos/options/ |
| wifi_config_view.cc | 573 // Connection failures are responsible for updating the UI, including
[all...] |
| /external/chromium/chrome/browser/history/ |
| expire_history_backend.cc | 570 // Ignore failures, we will delete it from the main DB no matter what.
|
| /external/chromium/chrome/browser/safe_browsing/ |
| protocol_manager.cc | 675 // Don't try too hard to send reports on failures.
|
| /external/chromium/net/base/ |
| net_error_list.h | 179 // Note that this does NOT include failures during the actual "CONNECT" method
|
| /external/chromium/net/http/ |
| http_stream_factory_impl_job.cc | 922 // "address unreachable" error, and will report both of these failures as
[all...] |
| /external/chromium/testing/gtest/ |
| README | 13 failures, various options for running the tests, and XML test report
|
| /external/clang/tools/scan-view/ |
| ScanView.py | 433 c.title = 'clang static analyzer failures'
|
| /external/dbus/cmake/ |
| CMakeLists.txt | 574 message("NOTE: building with unit tests but without assertions means tests may not properly report failures (this configuration is only useful when doing something like profiling the tests)")
|
| /external/dbus/dbus/ |
| dbus-internals.c | 963 _dbus_verbose ("\n===\n%s: (will fail malloc %d with %d failures)\n===\n",
|
| dbus-sysdeps-util-unix.c | 107 /* silently ignore failures here, if someone
|
| /external/e2fsprogs/e2fsck/ |
| crc32.c | 565 printf("\nAll test complete. No failures expected.\n");
|
| recovery.c | 640 * Hence to avoid checksum failures, in this
|
| /external/e2fsprogs/lib/et/ |
| com_err.texinfo | 406 failures of internal invariants and consistancy checks only, as it
|
| /external/icu4c/data/brkitr/ |
| line.txt | 189 # Chaining is disabled with CM because it causes other failures,
|
