Searched
full:iterations (Results
501 -
525 of
911) sorted by null
<<21222324252627282930>>
/cts/tests/tests/mediastress/src/android/mediastress/cts/ |
MediaRecorderStressTest.java | 382 Log.v(TAG, "iterations : " + i);
|
/cts/tests/tests/opengl/src/android/opengl/cts/ |
WrapperTest.java | 158 * killed within a couple hundred iterations.
|
/dalvik/vm/test/ |
AtomicTest.cpp | 335 dvmFprintf(stdout, "Same iterations done serially: time is %.6fms\n",
|
/external/apache-xml/src/main/java/org/apache/xpath/objects/ |
XNumber.java | 417 * iterations within the expression. This is used to determine if a proximity
|
/external/apache-xml/src/main/java/org/apache/xpath/operations/ |
Variable.java | 309 * iterations within the expression. This is used to determine if a proximity
|
/external/ceres-solver/internal/ceres/ |
line_search.h | 116 // Maximum number of trial step size iterations during each line search,
|
linear_solver.h | 99 // Number of internal iterations that the solver uses. This
|
program_evaluator.h | 160 // without breaking out of it. The remaining loop iterations are still run,
|
/external/chromium/chrome/browser/history/ |
expire_history_backend.h | 272 // iterations.
|
/external/chromium/chrome/browser/ui/gtk/ |
status_bubble_gtk.cc | 286 // toolbar" that I can find. Maybe in later iterations of the theme system,
|
/external/chromium/testing/gtest/test/ |
gtest_shuffle_test.py | 262 # Get the test lists in all 3 iterations, using random seed 1, 2,
|
/external/chromium_org/android_webview/javatests/src/org/chromium/android_webview/test/ |
AndroidViewIntegrationTest.java | 233 // This means that we hit the max number of iterations but the expected contents size
|
/external/chromium_org/base/test/launcher/ |
test_results_tracker.cc | 213 fprintf(stdout, "Summary of all itest iterations:\n");
|
/external/chromium_org/chrome/browser/extensions/api/declarative_content/ |
declarative_content_apitest.cc | 132 // matching-selector update. This also takes 2 iterations.
|
/external/chromium_org/chrome/browser/history/ |
expire_history_backend.h | 275 // iterations.
|
/external/chromium_org/chrome/browser/ui/gtk/ |
status_bubble_gtk.cc | 299 // toolbar" that I can find. Maybe in later iterations of the theme system,
|
/external/chromium_org/chrome/renderer/safe_browsing/ |
phishing_term_feature_extractor.cc | 67 // The number of iterations we've done for the current extraction.
|
phishing_term_feature_extractor_unittest.cc | 204 // iterations by incrementing the clock.
|
/external/chromium_org/chrome/test/functional/media/ |
media_jerky.py | 59 # Minimum and maximum number of iterations for each test. Due to timing issues
|
/external/chromium_org/content/browser/renderer_host/media/ |
web_contents_audio_input_stream_unittest.cc | 364 // Note: Arbitrarily chosen, but more iterations causes tests to take
|
/external/chromium_org/net/disk_cache/ |
stress_cache.cc | 136 // kNumKeys is meant to be enough to have about 3x or 4x iterations before
|
/external/chromium_org/testing/gtest/test/ |
gtest_shuffle_test.py | 262 # Get the test lists in all 3 iterations, using random seed 1, 2,
|
/external/chromium_org/third_party/WebKit/PerformanceTests/resources/ |
runner.js | 157 // FIXME: Don't hard code the number of in-process iterations to use inside a test runner.
|
/external/chromium_org/third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/views/ |
printing_unittest.py | 234 self.assertWritten(err, ["Found 100 tests; running 10 (6 times each: --repeat-each=2 --iterations=3), skipping 90.\n"])
|
/external/chromium_org/third_party/icu/source/test/perf/ustrperf/ |
stringperf.h | 22 #define LOOPS 100 //Iterations
|
Completed in 938 milliseconds
<<21222324252627282930>>