summaryrefslogtreecommitdiffstats
path: root/lldb/test/functionalities/platform
Commit message (Collapse)AuthorAgeFilesLines
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-281-65/+0
| | | | | | | | | | | This is the conclusion of an effort to get LLDB's Python code structured into a bona-fide Python package. This has a number of benefits, but most notably the ability to more easily share Python code between different but related pieces of LLDB's Python infrastructure (for example, `scripts` can now share code with `test`). llvm-svn: 251532
* Rename `lldb_shared` to `use_lldb_suite`.Zachary Turner2015-10-271-1/+1
| | | | llvm-svn: 251444
* Add from __future__ import print_function everywhere.Zachary Turner2015-10-231-0/+2
| | | | | | | | | | | | | Apparently there were tons of instances I missed last time, I guess I accidentally ran 2to3 non-recursively. This should be every occurrence of a print statement fixed to use a print function as well as from __future__ import print_function being added to every file. After this patch print statements will stop working everywhere in the test suite, and the print function should be used instead. llvm-svn: 251121
* Update every test to import `lldb_shared`.Zachary Turner2015-10-221-8/+2
| | | | | | | | | | | | | | | | | | | | | This is necessary in order to allow third party modules to be located under lldb/third_party rather than under the test folder directly. Since we're already touching every test file anyway, we also go ahead and delete the unittest2 import and main block wherever possible. The ability to run a test as a standalone file has already been broken for some time, and if we decide we want this back, we should use unittest instead of unittest2. A few places could not have the import of unittest2 removed,because they depend on the unittest2.expectedFailure or skip decorators. Removing all those was orthogonal in spirit to the purpose of this CL, so the import of unittest2 remains in those files that were using it for its test decorators. Those can be addressed separately. llvm-svn: 251055
* Merge dwarf and dsym testsTamas Berghammer2015-09-301-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently most of the test files have a separate dwarf and a separate dsym test with almost identical content (only the build step is different). With adding dwo symbol file handling to the test suit it would increase this to a 3-way duplication. The purpose of this change is to eliminate this redundancy with generating 2 test case (one dwarf and one dsym) for each test function specified (dwo handling will be added at a later commit). Main design goals: * There should be no boilerplate code in each test file to support the multiple debug info in most of the tests (custom scenarios are acceptable in special cases) so adding a new test case is easier and we can't miss one of the debug info type. * In case of a test failure, the debug symbols used during the test run have to be cleanly visible from the output of dotest.py to make debugging easier both from build bot logs and from local test runs * Each test case should have a unique, fully qualified name so we can run exactly 1 test with "-f <test-case>.<test-function>" syntax * Test output should be grouped based on test files the same way as it happens now (displaying dwarf/dsym results separately isn't preferable) Proposed solution (main logic in lldbtest.py, rest of them are test cases fixed up for the new style): * Have only 1 test fuction in the test files what will run for all debug info separately and this test function should call just "self.build(...)" to build an inferior with the right debug info * When a class is created by python (the class object, not the class instance), we will generate a new test method for each debug info format in the test class with the name "<test-function>_<debug-info>" and remove the original test method. This way unittest2 see multiple test methods (1 for each debug info, pretty much as of now) and will handle the test selection and the failure reporting correctly (the debug info will be visible from the end of the test name) * Add new annotation @no_debug_info_test to disable the generation of multiple tests for each debug info format when the test don't have an inferior Differential revision: http://reviews.llvm.org/D13028 llvm-svn: 248883
* Remove expectedFailureFreeBSD from passing test_process_listEd Maste2015-09-141-1/+0
| | | | | | | | | | | This test passes locally but was marked XFAIL due to failures on the FreeBSD buildbot. That buildbot has been retired as it was overloaded, and we will investigate again if this fails once a new buildbot is in place. llvm.org/pr23747 llvm-svn: 247562
* XFAIL TestPlatformCommand test failing on the FreeBSD buildbotEd Maste2015-06-031-0/+1
| | | | | | llvm.org/pr23747 llvm-svn: 238976
* Fix expectation for TestPlatformCommand.test_shellTamas Berghammer2015-03-041-1/+4
| | | | | | | | | * Create expectation based on target platform * Add custom expectation for remote android target Differential revision: http://reviews.llvm.org/D8031 llvm-svn: 231232
* Fix platform shell test to run "dir c:\" instead of "ls /" on Windows.Zachary Turner2014-12-081-2/+4
| | | | llvm-svn: 223700
* Update to match strings output by lldb.Jason Molenda2014-10-021-1/+1
| | | | llvm-svn: 218853
* Massive test suite cleanup to stop everyone from manually having to compute ↵Greg Clayton2013-12-101-1/+1
| | | | | | | | | | "mydir" inside each test case. This has led to many test suite failures because of copy and paste where new test cases were based off of other test cases and the "mydir" variable wasn't updated. Now you can call your superclasses "compute_mydir()" function with "__file__" as the sole argument and the relative path will be computed for you. llvm-svn: 196985
* Remove annotation for a test that now passes on FreeBSDEd Maste2013-08-301-1/+0
| | | | | | | | | | A FreeBSD implementation of Host::FindProcesses was added in r189295. Note that some tests still fail as the implementation returns a truncated name for processes with long names. http://www.llvm.org/pr16699 llvm-svn: 189667
* Fix 'platform shell' command for Linux host and remote lldb-platform connectionsDaniel Malea2013-08-271-0/+17
| | | | | | | - add default timeout of 10s (unil qPlatform_RunCommand supports timeout packets and CommandObjectPlatform is updated to read a timeout flag/setting) - add a few tests for platform shell llvm-svn: 189405
* tests: Mark expected FreeBSD failures due to pr16699Ed Maste2013-07-251-0/+1
| | | | | | | | FreeBSD's Host class doesn't yet return a list of running processes, so 'platform process list' fails and attach by process name does not work. llvm-svn: 187142
* Fix Linux 'platform status' command. Its output is now closer to that on Mac ↵Daniel Malea2013-05-161-1/+0
| | | | | | | | | | OS X - resolves llvm.org/pr14806 Patch by Matthew Sorrels! llvm-svn: 182030
* Clean up linux test decorators and add links to known bugsDaniel Malea2013-05-151-1/+1
| | | | | | | | | - s/skipOnLinux/skipIfLinux/ to match style of every other decorator - linkify bugizilla/PR numbers in comments No intended change in functionality. llvm-svn: 181913
* Re-enable tests disabled due to llvm.org/pr14541Daniel Malea2013-05-151-1/+0
| | | | | | | - "platform process list" command works on Linux now - "process attach -n" (attach to process by name also works on Linux now) llvm-svn: 181905
* Mark TestPlatformCommand (test_status) as expected to fail on LinuxDaniel Malea2013-01-051-1/+2
| | | | | | - due to bugzilla 14806 (platform status command prints more information on Mac OS X than on Linux) llvm-svn: 171569
* Test suite cleanup for Linux: mark test cases expected to fail due to open ↵Daniel Malea2012-12-191-0/+1
| | | | | | | | bugzillas - bugzillas covered: 14323, 14600, 14541, 14437, 14540, 14541 llvm-svn: 170564
* Move top level test dirs platform and inferior-crashing to reside under ↵Johnny Chen2011-06-271-0/+39
functionalities and order to reside under macosx. llvm-svn: 133919
OpenPOWER on IntegriCloud