summaryrefslogtreecommitdiffstats
path: root/lldb/test/lldbtest.py
Commit message (Collapse)AuthorAgeFilesLines
...
* [lldbtest] Use netloc instead of hostname to look up Android device ID.Siva Chandra2015-06-051-5/+7
| | | | | | | | | | | | | | | | | | | | | Summary: urlparse.ParseResult.hostname has only lowercase characters even if the input URL had uppercase characters. Since Android device IDs can have uppercase characters as well, use urlparse.ParseResult.netloc instead and extract the device ID from it. This change also improves the error message when lookup of the Android device's API fails. Reviewers: chaoren Reviewed By: chaoren Subscribers: tberghammer, lldb-commits Differential Revision: http://reviews.llvm.org/D10278 llvm-svn: 239173
* [TestChangeProcessGroup] Mark the test as xfail for Android API 16Siva Chandra2015-06-051-2/+43
| | | | | | | | | | | | | | | | | | Summary: This change adds the infrastructure to mark tests as xfail for specific Android API levels. Test Plan: dotest.py TestChangeProcessGroup on an Android API 16 device. Reviewers: chying, labath, chaoren Reviewed By: labath, chaoren Subscribers: tberghammer, lldb-commits Differential Revision: http://reviews.llvm.org/D10261 llvm-svn: 239126
* XFAIL two tests for androidPavel Labath2015-05-291-0/+6
| | | | | | bug #23694 llvm-svn: 238558
* [TestBase.runCmd] Better error message when runCmd fails.Siva Chandra2015-05-271-6/+16
| | | | | | | | | | | | | | | | | | | | | Summary: Before: AssertionError: False is not True : Process is launched successfully After: AssertionError: False is not True : Command 'run a.out' failed. >>> error: invalid target, create a target using the 'target create' command >>> Process could not be launched successfully Reviewers: clayborg Reviewed By: clayborg Subscribers: lldb-commits, vharron Differential Revision: http://reviews.llvm.org/D9948 llvm-svn: 238363
* Also don't try to copy a logfile if it doesn't exist.Zachary Turner2015-05-261-9/+10
| | | | | | | In some cases no log file will be written, so don't attempt to call os.rename() with a non-existent source path. llvm-svn: 238248
* On Windows, delete existing log file before renaming temp file.Zachary Turner2015-05-261-0/+7
| | | | | | | | | | On non-Windows platforms, os.rename() will silently replace the destination file if it already exists. On Windows, it doesn't do this, and the filesystem has no mechanism to simulate the same type of atomic rename operation. So on Windows, delete the file first before calling os.rename(). llvm-svn: 238239
* Don't import module `lock` at global scope.Zachary Turner2015-05-211-1/+1
| | | | | | | | `lock` depends on `fcntl`, which doesn't exist on Windows. Until someone implements an equivalent locking mechanism on Windows, we can't have lock imported globally. llvm-svn: 237946
* dotest.py - debug feature that helps find dosep racesVince Harron2015-05-211-2/+30
| | | | | | | | | | | | | | | | | | | | | | SUMMARY dosep.py starts lots and lots of dotest instances. This option helps you find if two (or more) dotest instances are using the same directory at the same time. Enable it to cause test failures and stderr messages if dotest instances try to run in the same directory simultaneously. It is disabled by default because it litters the test directories with ".dirlock" files TEST PLAN Set lldbtest.debug_confirm_directory_exclusivity = True run ./dosep.py Differential Revision: http://reviews.llvm.org/D9868 llvm-svn: 237935
* Re-enable packet logging for GdbRemote/LldbServer testsVince Harron2015-05-211-6/+5
| | | | | | | | Creates logs in session dir Differential Revision: http://reviews.llvm.org/D9847 llvm-svn: 237931
* dotest.py - log session to a file instead of a StringIO classVince Harron2015-05-211-24/+32
| | | | | | | | | | | | | That way, if the test gets killed (by a dosep timeout) we get to see the session trace Test Plan: Run dotest.py Kill it while it's running, check the session dir for Test* files Differential Revision: http://reviews.llvm.org/D9845 llvm-svn: 237926
* Refactored lldb executable name discoveryVince Harron2015-05-181-11/+4
| | | | | | | | | | | | | | | | | | | | The lldb executable was referenced through the code by 7 different (effectively) global variables. global lldbExecutablePath global lldbExecutable os.environ['LLDB_EXEC'] os.environ['LLDB_TEST'] dotest.lldbExec dotest.lldbHere lldbtest.lldbExec This change uses one global variable lldbtest_config.lldbExec to replace them all. Differential Revision: http://reviews.llvm.org/D9817 llvm-svn: 237600
* Choose stdlib for test suite based on target platform.Robert Flack2015-05-151-7/+7
| | | | | | | | | | | | | | When compiling programs for the test suite we currently choose which stdlib to use based on the host platform, but should be basing this on the target platform. Test Plan: ./dotest.py $DOTEST_OPTS -t -p TestThreadExit.py This test previously failed mac->linux most of the time due to using the mac host's atomic declaration. Differential Revision: http://reviews.llvm.org/D9797 llvm-svn: 237466
* Skip TestPluginCommands.py if host lldb library is incompatible with remote.Robert Flack2015-05-151-1/+35
| | | | | | | | | | | | | | | TestPluginCommands.py attempts to build a library which links against the host built lldb library. This will only work if the remote is compatible with binaries produced by the host. Test Plan: ./dotest.py $DOTEST_OPTS -v -t -p TestPluginCommands.py Test is skipped if remote platform is incompatible with host platform (i.e. mac -> linux). Differential Revision: http://reviews.llvm.org/D9770 llvm-svn: 237444
* Select expected remote libc++ library name based on remote platform.Robert Flack2015-05-131-1/+1
| | | | | | | | | | | | | | | | | | Select expected remote libc++ library name based on remote platform. This is used to verify libc++ is in the loaded image list by various tests which use it. Test Plan: Passes the following tests mac -> linux with this patch: TestDataFormatterLibccIterator.py TestDataFormatterLibccMap.py TestDataFormatterLibccMultiMap.py TestDataFormatterLibcxxMultiSet.py TestDataFormatterLibcxxSet.py TestDataFormatterUnordered.py Differential Revision: http://reviews.llvm.org/D9759 llvm-svn: 237288
* Change session log filename pattern: test before archVince Harron2015-05-121-2/+2
| | | | | | | | | | | | | | | | | | | | This is a very minor change. Just reshuffle the elements of the log filename so that the test name comes before the arch/compiler Before: Failure-x86_64-clang-TestCModules.CModulesTestCase.test_expr_with_dwarf.log After: Failure-TestCModules.CModulesTestCase.test_expr_with_dwarf-x86_64-clang.log This way, results are grouped by test name, not by arch. I think this is much more useful. Differential Revision: http://reviews.llvm.org/D9648 llvm-svn: 237076
* os.path.join does not always work for paths on remote platforms.Chaoren Lin2015-05-111-12/+11
| | | | | | | | | | | | | | | | Summary: Since we don't yet have remote windows debugging, it should be safe to assume that the remote target uses unix path separators. Reviewers: ovyalov, zturner, clayborg, vharron Reviewed By: vharron Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9633 llvm-svn: 237006
* Fixed lldb-mi test failures introduced by r236956Vince Harron2015-05-101-85/+68
| | | | | | | Move enable/disableLogForCurrentTest from lldbtest.TestBase to lldbtest.Base so they're accessible to Mi tests llvm-svn: 236963
* Add support for ./dotest.py --channel and --log-successVince Harron2015-05-101-15/+123
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: New dotest options that allow arbitrary log channels and categories to be enabled. Also enables logging for locally run debug servers. Log messages are separated into separate files per test case. (this makes it possible to log in dosep runs) These new log files are stored side-by-side with trace files in the session directory. These files are deleted by default if the test run is successful. If --log-success is specified, even successful logs are retained. --log-success is useful for creating reference log files. Test Plan: add '--channel "lldb all" --channel "gdb-remote packets" --log-success' to your dotest options Tested on OSX and Linux Differential Revision: http://reviews.llvm.org/D9594 llvm-svn: 236956
* Fixed skipIfLinuxClang to check the target architectureVince Harron2015-05-041-2/+2
| | | | | | | | | Instead of the host architecture This decorator isn't in use anywhere currently. Add it to a test and run llvm-svn: 236402
* Enabled libc++ formatter tests on LinuxVince Harron2015-05-041-1/+1
| | | | | | | | | | Refactored TestInitializerList to not be an inline test. Refactored Makefiles to use USE_LIBCPP instead of adding FLAGS directly Fixed copy/paste error in TestDataFormatterUnordered class name Differenttial Revision: http://reviews.llvm.org/D9426 llvm-svn: 236401
* TestMultithreaded improvementsVince Harron2015-05-041-0/+24
| | | | | | | | | | | | | | These tests link against host lldb API. Compiler's target triple must match liblldb triple. Instead of naively skipping i386, I added a check of the liblldb arch against the compiler target arch. This is useful for 32 bit API builds (planned for Windows) Since remote is disabled, we can assume the os is the same. Also, removed skipIfLinuxClang because it's passing llvm-svn: 236396
* XFAIL tests that are failed on linux with gcc-4.9.2Ying Chen2015-04-211-0/+55
| | | | | | | | | | | | | | | | | | | Summary: - add decorator functions to xfail and skip test on specific os, architecture and version of comipler - xfail failing test with gcc-4.9.2 on linux - add one usage of skipIf function Test Plan: Run tests with different archs, and version of compilers to verify decorator function working as expected Run tests with gcc-4.9.2 and no failure reported Reviewers: sivachandra, ovyalov, vharron, chaoren Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8851 llvm-svn: 235368
* Uses the target platform to determine the platform context.Robert Flack2015-04-171-11/+10
| | | | | | | | | | | | | | | Uses the target platform to determine the platform context to use. This fixes an early failure in some tests when running on a different remote target. Test Plan: ./dotest.py $DOTEST_OPTS -t -p TestGlobalVariables.py|TestSharedLib.py Running on macosx -> linux, this fails at a later stage in the test - rather than in registerSharedLibrariesWithTarget looking for a library without the correct "lib" prefix and ".so" suffix. Differential Revision: http://reviews.llvm.org/D9047 llvm-svn: 235164
* Bug 23051 - Fix zombie processes after lldb-server testsIlia K2015-04-151-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: This patch fixes the following bug: https://llvm.org/bugs/show_bug.cgi?id=23181 For some reason some lldb-server tests should be kicked using SIGHUP and SIGINT before termination, otherwise it will leave a zombie process. I think the reason is that the lldb-server will terminate a slave process if it gets the SIGHUP/SIGINT and if so it should be fixed in lldb-server. The solution is to terminate process like it does the pexpect (including the delayafterterminate interval). Also this patch reverts the following commits: * r234549 - Skip lldb-server tests according to bug 23181 * r234765 - Skip a few tests on OS X according to the bug 23181 * r234803 - Skip the TestGdbRemoteRegisterState.test_grp_register_save_restore_works_no_suffix_debugserver_dsym test on OS X according to the bug 23181 Test Plan: ``` $ ps | grep Z | grep a.out | wc -l 447 $ ./dosep.py --options "-v --executable $INSTALLDIR/bin/lldb" [...] $ ps | grep Z | grep a.out | wc -l 447 ``` Reviewers: jasonmolenda, clayborg, tberghammer Reviewed By: clayborg Subscribers: lldb-commits, dawn, tberghammer, clayborg, jasonmolenda Differential Revision: http://reviews.llvm.org/D9019 llvm-svn: 235008
* Fix @skipUnlessPlatform and @skipIfPlatform decorators to work on classes.Robert Flack2015-04-091-26/+11
| | | | | | | | | | | | | | | | The decorators to skip if or unless certain platforms relied on calling skipTest, which only worked if they were decorating individual test cases. However for decorating entire classes it needs different behavior. This behavior is already encapsulated in unittest2.skipIf and unittest2.skipUnless so this modifies the platform decorators to use these unittest skip decorators. Test Plan: ./dotest.py -t -p TestObjCMethods2.py See skipped tests on linux, and see tests run on macosx. Differential Revision: http://reviews.llvm.org/D8903 llvm-svn: 234514
* Fix expectedFailureLLGS to expect failure when host platform is not linux.Robert Flack2015-04-091-2/+2
| | | | | | | | | | | | | | | expectedFailureLLGS has an early return false if the platform is not linux except it should be checking the target platform on which the server is running for remote tests. Test Plan: Verify expected failure when running from mac to remote linux llgs: TestBreakAfterJoin.py, TestCreateDuringStep.py, TestExitDuringBreak.py, TestProcessLaunch.py, TestThreadStates.py Differential Revision: http://reviews.llvm.org/D8869 llvm-svn: 234492
* test: Move amd64 -> x86_64 translation to getArchitecture()Ed Maste2015-04-061-1/+4
| | | | | | | Rather than sprinkling this knowledge throughout the test suite, just translate amd64 to x86_64 globally. llvm-svn: 234166
* Fix LLDB test tracing to include the output (stdout and stderr) of each ↵Adrian McCarthy2015-04-031-2/+2
| | | | | | shell command. llvm-svn: 234025
* TestRecursiveInferior fixed on LinuxVince Harron2015-04-031-0/+5
| | | | | | | | | | | | | | | | | Summary: Updated test to reflect that Linux and Darwin behave the same now. Removed @expectedFailureLinux for passing tests. Test Plan: run tests Reviewers: clayborg, sivachandra Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D8678 llvm-svn: 233989
* Many many test failures after some recent changes. The problem is ↵Greg Clayton2015-04-021-3/+11
| | | | | | | | | | | | | | | | lldbtest.getPlatform() returns the "OS" of the selected platform's triple. This is "macosx" for desktop macosx and "ios" for iOS. It used to be "darwin". There was a lot of code that was checking "if self.getPlatform() == 'darwin'" which is not correct. I fixed this by adding a: lldbtest.platformIsDarwin() which returns true if the current platform's OS is "macosx", "ios" or "darwin". These three valid darwin are now returned by a static function: lldbtest.getDarwinOSTriples() Fixed up all places that has 'if self.getPlatform() == "darwin":' with "if self.platformIsDarwin()" and all instances of 'if self.getPlatform() != "darwin":' with "if not self.platformIsDarwin()". I also fixed some darwin decorator functions to do the right thing as well. llvm-svn: 233933
* Fix FreeBSD test runs after r233311Ed Maste2015-03-311-1/+4
| | | | | | | | On FreeBSD LLDB's triple ends up as e.g. "x86_64-unknown-freebsd10.1" but getPlatform() consumers expect just the name with no version number. llvm-svn: 233705
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-301-57/+48
| | | | | | | | | | | | | | | | against remote platform. Adds @skipIfPlatform and @skipUnlessPlatform decorators which will skip if / unless the target platform is in the provided platform list. Test Plan: ninja check-lldb shows no regressions. When running cross platform, tests which cannot run on the target platform are skipped. Differential Revision: http://reviews.llvm.org/D8665 llvm-svn: 233547
* Fix lld command on Windows for many tests.Adrian McCarthy2015-03-271-2/+12
| | | | llvm-svn: 233416
* Allow ExpectedFailure* decorators to work with optional argumentsYing Chen2015-03-271-18/+19
| | | | | | -if the decorator functions called with optional arguments, return decorator to orignal method llvm-svn: 233338
* Change expectedFailureOS and skipIfPlatform checks to be based on target ↵Robert Flack2015-03-261-12/+14
| | | | | | | | | | | | | | | | | platform when running test suite remotely. Most expected OS failures or skipped tests are about the target platform on which the test binary is being run, not the host platform launching the tests. This changes expectedFailureOS and skipIfPlatform to check against the remote platform when running remote tests. Test Plan: Run ./do_sep.py test suite against a remote target on a different platform and verify that tests which should be excluded on the remote platform are excluded. Differential Revision: http://reviews.llvm.org/D8611 llvm-svn: 233311
* Fix test failures caused by order of initialization.Zachary Turner2015-03-261-2/+4
| | | | | | | | | tear down hooks run as part of Base.tearDown(). Some of these hooks rely on accessing the debugger instance. So although it looks awkward, we need to call "del self.dbg" after calling Base.tearDown(). llvm-svn: 233306
* Tear down tests in reverse order from setting them up.Zachary Turner2015-03-261-35/+36
| | | | | | | | | | | | | | | | | | | | Tests derive from TestBase, which derives from Base. In the test setUp() methods, we always call TestBase.setUp() first and then call implementation-specific setup. Tear down needs to do the reverse. This was causing over 20 failures on Windows, and was the culprit behind about 80% of the files not being cleaned up after test run. TestBase.tearDown() is responsible for deleting all targets created during the test run and without this step, on Windows files will be locked and cannot be deleted. But TestBase.tearDown() was calling Base.tearDown() before its own cleanup (i.e. deleting the targets) and in some cases one of the teardown hooks would be to call make clean. So make clean would be run before the targets had been deleted, and fail to remove the files, and subsequently result in a failed test as well. llvm-svn: 233284
* Fix not_remote_testsuite_ready annotation in the test runnerTamas Berghammer2015-03-251-1/+1
| | | | | | Treat a test run as remote run also if lldb.remote_platform is set. llvm-svn: 233190
* Fix makefiles to build shared library tests on Windows.Zachary Turner2015-03-131-1/+1
| | | | | | | | | | | | | | | Abstracted away some POSIX-isms that caused MAKE to issue invalid commands on Windows. Added a new force-include for the test programs so that we can use platform-specific macros. TestSharedLib now builds and cleans up on Windows, though the test still fails some of the expectations. Differential Revision: http://reviews.llvm.org/D8277 Patch by: Adrian McCarthy Issue Tracker: http://llvm.org/pr21727 llvm-svn: 232220
* Add support for XFAILing a test on specific clang versionsVince Harron2015-03-131-2/+4
| | | | llvm-svn: 232205
* Skip fdleak tests on androidTamas Berghammer2015-03-131-0/+15
| | | | | | | | | Android have more file descriptor opened by the shell what are inherited to the process (different ones on device and on emulator). Differential revision: http://reviews.llvm.org/D8299 llvm-svn: 232150
* Limit the lenght of the file name of the log file for testsTamas Berghammer2015-03-121-2/+5
| | | | | | | | | | | If a test have very long name and the compiler specified with (a long) full path then the name of the log file name can exceed 255 characters. This change replace the full compiler path with just the compiler name if the prior would cause a too long file name. Differential revision: http://reviews.llvm.org/D8252 llvm-svn: 232024
* Skip AsanTestCase and AsanTestReportDataCase on DarwinIlia K2015-03-121-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: This patch skips tests which cause the following error: ``` 1: test_with_dsym (TestMemoryHistory.AsanTestCase) ... os command: make clean ; make MAKE_DSYM=YES ARCH=x86_64 CC="/Users/IliaK/p/llvm/build_ninja/bin/clang" with pid: 9475 stdout: rm -f "a.out" main.o main.d main.d.tmp rm -f -r "a.out.dSYM" /Users/IliaK/p/llvm/build_ninja/bin/clang -fsanitize=address -fsanitize-address-field-padding=1 -g -arch x86_64 -I/Users/IliaK/p/llvm/tools/lldb/test/make/../../include -c -o main.o main.c /Users/IliaK/p/llvm/build_ninja/bin/clang main.o -fsanitize=address -fsanitize-address-field-padding=1 -g -arch x86_64 -I/Users/IliaK/p/llvm/tools/lldb/test/make/../../include -o "a.out" stderr: clang: error: unknown argument: '-fsanitize-address-field-padding=1' clang: error: unsupported argument 'address' to option 'fsanitize=' ld: file not found: /Users/IliaK/p/llvm/build_ninja/bin/../lib/clang/3.7.0/lib/darwin/libclang_rt.asan_osx_dynamic.dylib clang-3.7: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [a.out] Error 1 retcode: 2 ERROR os command: make clean with pid: 9521 stdout: rm -f "a.out" main.o main.d main.d.tmp rm -f -r "a.out.dSYM" stderr: retcode: 0 Restore dir to: /Users/IliaK/p/llvm/tools/lldb ====================================================================== ERROR: test_with_dsym (TestMemoryHistory.AsanTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 612, in wrapper func(*args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 456, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/asan/TestMemoryHistory.py", line 24, in test_with_dsym self.buildDsym (None, compiler) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 1496, in buildDsym if not module.buildDsym(self, architecture, compiler, dictionary, clean): File "/Users/IliaK/p/llvm/tools/lldb/test/plugins/builder_darwin.py", line 16, in buildDsym lldbtest.system(commands, sender=sender) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 370, in system raise CalledProcessError(retcode, cmd) CalledProcessError: Command 'make clean ; make MAKE_DSYM=YES ARCH=x86_64 CC="/Users/IliaK/p/llvm/build_ninja/bin/clang" ' returned non-zero exit status 2 Config=x86_64-clang ---------------------------------------------------------------------- ``` Also this patch fixes findBuiltClang() by looking a clang in the build folder. BTW, another patch was made in October 2014, but it wasn't committed: http://reviews.llvm.org/D6272. Reviewers: abidh, zturner, emaste, jingham, jasonmolenda, granata.enrico, DougSnyder, clayborg Reviewed By: clayborg Subscribers: lldb-commits, DougSnyder, granata.enrico, jasonmolenda, jingham, emaste, zturner, abidh, clayborg Differential Revision: http://reviews.llvm.org/D7958 llvm-svn: 232016
* Refactor GdbRemote test cases to support remote platformsTamas Berghammer2015-03-111-13/+19
| | | | | | | | | | | Previously these test cases execute lldb-server on the host and run the tests against it even if a remote platform was specified. With this CL these tests always test the communication with an lldb-server instance running on the target. Differential revision: http://reviews.llvm.org/D8202 llvm-svn: 231922
* Rename test/tools/lldb-gdbserver to test/tools/lldb-serverRobert Flack2015-03-061-1/+1
| | | | | | | | As requested in http://reviews.llvm.org/D7545 this change moves test/tools/lldb-gdbserver to test/tools/lldb-server ot match the name of the target being tested. Differential Revision: http://reviews.llvm.org/D8061 llvm-svn: 231479
* Linux - debugging of local processes via lldb-gdbserverVince Harron2015-03-011-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of lldb calling the ptrace APIs directly, it launches an llgs instance and communicates with it via the remote debug protocol. This has two advantages. There is more code shared between the remote debugging code path and the local debugging code path. If a feature works in remote, it probably works locally and vice-versa. It makes us more architecturally similar to OSX (which also does local debugging via a connection to debugserver). This path is called LLGS local. We think that this configuration is now at parity with (or better than) local linux debugging. It is currently invoked if you have an environment variable defined "PLATFORM_LINUX_FORCE_LLGS_LOCAL" We would like to switch to LLGS local as the default path and only use the non-LLGS path if someone has an environment variable defined "PLATFORM_LINUX_DISABLE_LLGS_LOCAL" Later, if all goes well, we would like to remove non-LLGS local debugging support to simplify the codebase and avoid confusion. llvm-svn: 230919
* Remove use_pthread option from getBuildFlags in the test environmentTamas Berghammer2015-02-251-4/+2
| | | | | | | | | | | Removing the option to require the usage of pthread based on an argument of the getBuildFlags method in lldbtest.py because it can be specified by a variable in the makefile for the given test case. Using the variable in the makefile works in all supported platforms. Differential revision: http://reviews.llvm.org/D7861 llvm-svn: 230493
* Except only EIO errors of OSError exception in Base.deletePexpectChild() in ↵Ilia K2015-02-111-1/+8
| | | | | | lldbtest.py after r227086 llvm-svn: 228877
* Extend SBPlatform with capability to launch/terminate a process remotely. ↵Oleksiy Vyalov2015-02-041-7/+77
| | | | | | | | Integrate this change into test framework in order to spawn processes on a remote target. http://reviews.llvm.org/D7263 llvm-svn: 228230
* Mark several tests as XFAIL with new expectedFailureLLGS decorator since ↵Chaoren Lin2015-02-031-0/+5
| | | | | | they are failing in Darwin for the same reason. llvm-svn: 227925
OpenPOWER on IntegriCloud