| /frameworks/base/tests/backup/ |
| D | backup_stress_test.sh | 18 failures=0
45 failures=$(($failures+1))
47 echo "FAILED iteration $i of $iterations; $failures failures so far"
48 echo "FAILED iteration $i of $iterations; $failures failures so far" > /dev/stderr
58 echo "DONE: $iterations iterations with $failures failures."
59 echo "DONE: $iterations iterations with $failures failures." > /dev/stderr
60 [ "$failures" -eq 0 ] && exit 0
|
| /frameworks/base/media/tests/SoundPoolTest/src/com/android/ |
| D | SoundPoolTest.java | 337 int failures = 0; in run() local
351 if (!TestSounds()) failures = failures + 1; in run()
352 if (!TestScales()) failures = failures + 1; in run()
353 if (!TestRates()) failures = failures + 1; in run()
354 if (!TestPriority()) failures = failures + 1; in run()
355 if (!TestVolume()) failures = failures + 1; in run()
359 if (!TestPauseResume()) failures = failures + 1; in run()
363 failures = failures + 1; in run()
376 if (failures == 0) { in run()
379 Log.i(LOG_TAG, failures + " tests failed"); in run()
|
| /frameworks/base/test-runner/tests/src/android/test/suitebuilder/ |
| D | UnitTestSuiteBuilderTest.java | 69 private Set<String> failures = new HashSet<String>(); field in UnitTestSuiteBuilderTest.SuiteExecutionRecorder
78 failures.add(testName(test)); in addFailure()
93 return failures.contains(testName); in failed()
|
| D | InstrumentationTestSuiteBuilderTest.java | 76 private Set<String> failures = new HashSet<String>(); field in InstrumentationTestSuiteBuilderTest.SuiteExecutionRecorder
85 failures.add(testName(test)); in addFailure()
100 return failures.contains(testName); in failed()
|
| D | TestSuiteBuilderTest.java | 178 private Set<String> failures = new HashSet<String>();
187 failures.add(testName(test));
202 return failures.contains(testName);
|
| /frameworks/base/tools/apilint/ |
| D | apilint.py | 240 failures = {} variable
244 global failures
249 failures[sig] = Failure(sig, clazz, detail, error, rule, msg)
1043 global failures
1044 failures = {}
1046 return failures
1051 global failures
1052 failures = {}
1055 return failures
1060 global failures
[all …]
|
| /frameworks/compile/slang/lit-tests/ |
| D | README | 18 When debugging failures, the "-v" option will print to stdout the details of
37 -v enables additional verbosity (useful when examining unexpected failures)
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
| D | EventLogTags.logtags | 21 # PDP Setup failures
|
| /frameworks/compile/libbcc/tests/debuginfo/host-tests/ |
| D | lit.cfg | 23 # the target triple string that must be used in cases marked expected failures
|
| /frameworks/compile/libbcc/tests/debuginfo/ |
| D | README | 58 -v enables additional verbosity (useful when examining unexpected failures)
|
| /frameworks/compile/libbcc/tests/debuginfo/target-tests/ |
| D | lit.cfg | 43 # the target triple string that must be used in cases marked expected failures
|
| /frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktest/stress/ |
| D | Camera2ReprocessCaptureTest.java | 556 ArrayList<CaptureFailure> failures = in testReprocessAbort() local
559 for (CaptureFailure failure : failures) { in testReprocessAbort()
|
| /frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktest/helpers/ |
| D | CameraTestUtils.java | 578 ArrayList<CaptureFailure> failures = new ArrayList<>(); in getCaptureFailures() local
587 failures.add(failure); in getCaptureFailures()
593 return failures; in getCaptureFailures()
|
| /frameworks/base/docs/html/training/wearables/apps/ |
| D | creating-app-china.jd | 141 To learn how to handle connection failures,
|
| /frameworks/support/buildSrc/src/main/groovy/android/support/checkapi/ |
| D | CheckApiTask.groovy | 312 // We will be handling failures ourselves with a custom message.
|
| /frameworks/base/services/core/java/com/android/server/ |
| D | NetworkManagementService.java | 2781 int failures = 0; in removeRoutesFromLocalNetwork() local
2787 failures++; in removeRoutesFromLocalNetwork()
2791 return failures; in removeRoutesFromLocalNetwork()
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-1.1.jd | 173 <li>Improves recovery from POP3 connection failures.</li>
|
| /frameworks/native/vulkan/doc/implementors_guide/ |
| D | implementors_guide.adoc | 34 … libraries directory). IHV and OEM engineers who are trying to diagnose failures in shipping, unmo…
|
| /frameworks/base/docs/html/training/id-auth/ |
| D | authenticate.jd | 161 are expected to handle these failures automatically.</p>
|
| /frameworks/base/docs/html/guide/practices/ |
| D | verifying-apps-art.jd | 207 This can lead to CheckJNI failures because of the unhandled exceptions or the
|
| /frameworks/base/docs/html/training/testing/unit-testing/ |
| D | instrumented-unit-tests.jd | 292 of any app failures.</p>
|
| /frameworks/base/docs/html/training/articles/ |
| D | perf-jni.jd | 594 <p>Another class of <code>UnsatisfiedLinkError</code> failures looks like:</p>
638 <p>(Most of this advice applies equally well to failures to find methods
|
| D | smp.jd | 1500 programming mistakes, but it will help you avoid the mysterious failures
1693 catches failures by thread 2 to observe writes to <code>a</code>, for example if we
1710 once. In practice, failures will be infrequent and difficult to locate. This
|
| /frameworks/base/docs/html/topic/performance/ |
| D | threads.jd | 100 can be exceptions, silent failures, crashes, and other undefined misbehavior.
|
| /frameworks/base/docs/html/training/testing/ui-testing/ |
| D | uiautomator-testing.jd | 348 element (for example, icons in a toolbar). Text selectors are brittle and can lead to test failures
|