HomeSort by relevance Sort by last modified time
    Searched full:after (Results 1351 - 1375 of 38973) sorted by null

<<51525354555657585960>>

  /external/autotest/server/site_tests/display_LidCloseOpen/
control.mirrored_unplug_close_plug_open 24 - suspend after unplug in docked mode
25 - resume after open
control.mirrored_unplug_close_plug_unplug_open_plug 24 - suspend after unplug in docked mode
25 - resume after open
control.mirrored_unplugged_combined 22 - suspend after unplug in docked mode
23 - resume after open
  /external/autotest/server/site_tests/logging_KernelCrashServer/
control 19 - kernel crash dump doesn't appear after crash
26 # and purge its content after each test pass. This test executes several
  /external/autotest/server/site_tests/platform_CryptohomeMigrateChapsToken/
platform_CryptohomeMigrateChapsToken.py 10 available after a ChromeOS autoupdate.
18 # Save the build on the DUT, because we want to provision it after
  /external/autotest/server/site_tests/platform_ServoPowerStateController/
platform_ServoPowerStateController.py 22 """Clean up DUT after servo actions."""
52 """Confirm DUT is off and does not turn back on after 30 seconds.
62 ' after it is turned off.'))
82 self.assert_dut_off('power_state:off failed after boot from external '
120 'on after power_on is completed.')
127 self.assert_dut_off('power_state:off failed after boot from '
130 logging.info('Power DUT off and reset. DUT should be on after '
135 logging.info('Reset DUT when it\'s on. DUT should be on after '
  /external/autotest/server/site_tests/sequences/
control.storage_qual_retention_quick 37 { 'tag': 'after', 'client_tag': 'after'}),
control.storage_qual_suspend_quick 35 {'tag': 'after', 'client_tag': 'after', 'crypto_runtime': 30}),
control.storage_qual_trim_quick 36 {'tag': 'after', 'client_tag': 'after', 'crypto_runtime': 30}),
  /external/chromium-trace/catapult/telemetry/telemetry/internal/actions/
repaint_continuously.py 15 out after max(60, self.seconds), if less than three RAFs were fired.
32 # fired. Use a hard time-out after 60 seconds (or self.seconds).
  /external/chromium-trace/catapult/telemetry/telemetry/web_perf/
story_test.py 42 """Override to do any action after running the story, e.g., clean up.
44 This is run after state.DidRunStory. And this is always called even if the
  /external/clang/test/Analysis/
objc-message.m 25 // We intentionally drop the nil flow (losing coverage) after a method
35 // Both the receiver and the result should be nil after a message
  /external/clang/test/CodeGenCXX/
sanitize-dtor-fn-attribute.cpp 1 // Test -fsanitize-memory-use-after-dtor
2 // RUN: %clang_cc1 -fsanitize=memory -fsanitize-memory-use-after-dtor -std=c++11 -triple=x86_64-pc-linux -emit-llvm -o - %s | FileCheck %s
  /external/compiler-rt/test/asan/TestCases/Posix/
current_allocated_bytes.cc 38 printf("After iteration %d: %zu\n", iter, used_mem);
42 printf("Success after %d iterations\n", kNumIterations);
  /external/compiler-rt/test/asan/TestCases/Windows/
fuse-lld.cc 5 // FIXME: Use -fuse-ld=lld after the old COFF linker is removed.
18 // CHECK: heap-use-after-free
  /external/compiler-rt/test/asan/TestCases/
max_redzone.cc 21 size_t after = __sanitizer_get_heap_size(); local
24 size_t diff = after - before;
printf-4.c 17 fputs("after sprintf", stderr);
22 // CHECK-ON-NOT: after sprintf
suppressions-function.cc 27 // CHECK-CRASH: AddressSanitizer: heap-use-after-free
29 // CHECK-IGNORE-NOT: AddressSanitizer: heap-use-after-free
suppressions-interceptor.cc 21 // CHECK-CRASH: AddressSanitizer: heap-use-after-free
23 // CHECK-IGNORE-NOT: AddressSanitizer: heap-use-after-free
suppressions-library.cc 39 // CHECK-CRASH: AddressSanitizer: heap-use-after-free
41 // CHECK-IGNORE-NOT: AddressSanitizer: heap-use-after-free
throw_catch.cc 30 fprintf(stderr, "After: %p poisoned: %d\n", &x,
49 fprintf(stderr, "After: %p poisoned: %d\n", &x,
  /external/compiler-rt/test/tsan/
fork_multithreaded.cc 39 // CHECK-DIE: ThreadSanitizer: starting new threads after multi-threaded fork is not supported
42 // CHECK-NODIE-NOT: ThreadSanitizer: starting new threads after multi-threaded fork is not supported
free_race.c 38 // CHECK-NOZUPP: WARNING: ThreadSanitizer: heap-use-after-free
45 // CHECK-NOZUPP: SUMMARY: ThreadSanitizer: heap-use-after-free{{.*}}Thread2
  /external/curl/tests/data/
test1517 16 # Force server reply right after request headers, not waiting for request body
52 # Verify data after the test has been "shot"
  /external/dnsmasq/contrib/port-forward/
portforward 25 # Port forwards will recreated when dnsmasq restarts after a reboot, and
26 # removed when DHCP leases expire. After editing this file, send

Completed in 545 milliseconds

<<51525354555657585960>>