maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Index/crash-recovery-code-complete.c

12 lines
457 B
C
Raw Normal View History

The two libclang crash-recovery tests that involve precompiled preambles end up leaving the precompiled preambles around. This is by design, since we do minimal cleanup during crash recovery. However, it's unfortunate for testing, so introduce a hook that allows these two tests to put the precompiled preamble somewhere where we can delete them after testing. llvm-svn: 113698
2010-09-12 02:05:19 +08:00
// RUN: env CINDEXTEST_EDITING=1 CINDEXTEST_PREAMBLE_FILE=%t-preamble.pch \
libclang: Execute clang_codeCompleteAt() inside a crash recovery context. - Test case is disabled for now, because something isn't write with file remapping. llvm-svn: 111581
2010-08-20 07:44:10 +08:00
// RUN: not c-index-test -code-completion-at=%s:20:1 \
When performing code-completion in the presence of a preamble, make sure to (1) actually use the remapped files we were given rather than old data, and (2) keep the remapped files alive until the code-completion results are destroyed. Big thanks to Daniel for the test case. llvm-svn: 111597
2010-08-20 08:59:43 +08:00
// RUN: "-remap-file=%s;%S/Inputs/crash-recovery-code-complete-remap.c" \
libclang: Execute clang_codeCompleteAt() inside a crash recovery context. - Test case is disabled for now, because something isn't write with file remapping. llvm-svn: 111581
2010-08-20 07:44:10 +08:00
// RUN: %s 2> %t.err
// RUN: FileCheck < %t.err -check-prefix=CHECK-CODE-COMPLETE-CRASH %s
The two libclang crash-recovery tests that involve precompiled preambles end up leaving the precompiled preambles around. This is by design, since we do minimal cleanup during crash recovery. However, it's unfortunate for testing, so introduce a hook that allows these two tests to put the precompiled preamble somewhere where we can delete them after testing. llvm-svn: 113698
2010-09-12 02:05:19 +08:00
// RUN: rm %t-preamble.pch
When performing code-completion in the presence of a preamble, make sure to (1) actually use the remapped files we were given rather than old data, and (2) keep the remapped files alive until the code-completion results are destroyed. Big thanks to Daniel for the test case. llvm-svn: 111597
2010-08-20 08:59:43 +08:00
// CHECK-CODE-COMPLETE-CRASH: Unable to perform code completion!
libclang: Execute clang_codeCompleteAt() inside a crash recovery context. - Test case is disabled for now, because something isn't write with file remapping. llvm-svn: 111581
2010-08-20 07:44:10 +08:00
//
tests: Use REQUIRES: instead of XFAIL: for crash recovery tests; running them on Windows breaks things (because it pops up dialogs) since we don't have crash recovery support there (yet). llvm-svn: 111970
2010-08-25 05:39:55 +08:00
// REQUIRES: crash-recovery
libclang: Execute clang_codeCompleteAt() inside a crash recovery context. - Test case is disabled for now, because something isn't write with file remapping. llvm-svn: 111581
2010-08-20 07:44:10 +08:00
#warning parsing original file