summaryrefslogtreecommitdiffstats
path: root/lldb/test/functionalities/process_attach/TestProcessAttach.py
Commit message (Collapse)AuthorAgeFilesLines
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-281-57/+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-7/+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-42/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Try to enable TestProcessAttach tests on Linux.Oleksiy Vyalov2015-07-081-6/+0
| | | | | | http://reviews.llvm.org/D11013 llvm-svn: 241702
* Add expectedFailureLinux to TestProcessAttachPavel Labath2015-04-301-2/+6
| | | | | | The test is skipped anyway due to timeout, but adding XFAIL improves grepability. llvm-svn: 236224
* Skip TestProcessAttach.py on LinuxPavel Labath2015-04-281-2/+2
| | | | | | | The test was already XFAILed. Changing this to skip, because the test timeouts and gets flagged as an error anyway. llvm-svn: 235979
* [TestProcessAttach] Decorate with expectedFailureLinuxSiva Chandra2015-04-271-0/+2
| | | | | | | | | | | | | | Summary: Link to PR: llvm.org/pr23360 Test Plan: dotest.py -p TestProcessAttach Reviewers: sivachandra Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9310 llvm-svn: 235947
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-301-2/+2
| | | | | | | | | | | | | | | | 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
* Destroy the attached process in tearDown() to fix ProcessAttachTestCase ↵Ilia K2015-03-261-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tests on OS X This patch fixes the following: ``` 1: test_attach_to_process_by_id_with_dsym (TestProcessAttach.ProcessAttachTestCase) Test attach by process id ... ok 2: test_attach_to_process_by_id_with_dwarf (TestProcessAttach.ProcessAttachTestCase) Test attach by process id ... ok 3: test_attach_to_process_by_name_with_dsym (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ... FAILURE 4: test_attach_to_process_by_name_with_dwarf (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ... FAILURE ====================================================================== FAIL: test_attach_to_process_by_name_with_dsym (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 462, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 35, in test_attach_to_process_by_name_with_dsym self.process_attach_by_name() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 79, in process_attach_by_name self.runCmd("process attach -n s" + exe_name) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2008, in runCmd msg if msg else CMD_MSG(cmd)) AssertionError: False is not True : Command 'process attach -n sProcessAttach' returns successfully Config=x86_64-clang ====================================================================== FAIL: test_attach_to_process_by_name_with_dwarf (TestProcessAttach.ProcessAttachTestCase) Test attach by process name ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 479, in wrapper return func(self, *args, **kwargs) File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 41, in test_attach_to_process_by_name_with_dwarf self.process_attach_by_name() File "/Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/TestProcessAttach.py", line 79, in process_attach_by_name self.runCmd("process attach -n s" + exe_name) File "/Users/IliaK/p/llvm/tools/lldb/test/lldbtest.py", line 2008, in runCmd msg if msg else CMD_MSG(cmd)) AssertionError: False is not True : Command 'process attach -n sProcessAttach' returns successfully Config=x86_64-clang ---------------------------------------------------------------------- ``` Failure-x86_64-clang-TestProcessAttach.ProcessAttachTestCase.test_attach_to_process_by_name_with_dsym.log: ``` [...] runCmd: process attach -n ProcessAttach runCmd failed! error: attach failed: more than one process named ProcessAttach: PID PARENT USER TRIPLE ARGUMENTS ====== ====== ========== ======================== ============================ 43752 43680 IliaK x86_64-apple-macosx /Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/ProcessAttach 43663 1 IliaK x86_64-apple-macosx /Users/IliaK/p/llvm/tools/lldb/test/functionalities/process_attach/ProcessAttach [...] ``` llvm-svn: 233272
* This commit provides support for running the dosep.ty test driver with ↵Steve Pucci2014-03-071-3/+5
| | | | | | | | | | | | | | multiple threads. It speeds up running the full test suite on my HP z620 Ubuntu machine with 32 hyperthreaded CPUs from 11 minutes to about 1m13s (about 9x). The default behavior is to run single-threaded as before. If the environment variable LLDB_TEST_THREADS is set, a Python work queue is set up with that many worker threads. To avoid collisions within a test directory where multiple tests make use of the same prebuilt executable, the unit of work for the worker threads is a single directory (that is, all tests within a directory are processed in the normal serial way by a single thread). tfiala & I have run this way a number of times; the only issue I found was that the TestProcessAttach.py test failed once, when attempting to attach to the process "a.out" by name. I assume this is because some other thread was running an executable of that name at the same time, and we were attempting to attach to the wrong one, so I changed that test to use a different executable name (that change is also included in this commit). llvm-svn: 203180
* 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
* Attach by name tests now pass on FreeBSDEd Maste2013-08-301-1/+0
| | | | | | | | | | A FreeBSD implementation of Host::FindProcesses was added in r189295. Contrary to my earlier report of failing tests it seems all attach by name tests now pass. http://www.llvm.org/pr16699 llvm-svn: 189680
* 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
* 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
* Fixed the process attach by name test to get the target _after_ doing ↵Greg Clayton2013-05-081-2/+2
| | | | | | process attach. Otherwise the target isn't valid. This fixes 2 test suite failures on darwin. llvm-svn: 181488
* Adding support for process attach by pid on Linux.Andrew Kaylor2013-05-071-3/+0
| | | | llvm-svn: 181374
* Fixed a test suite typo error that caused the test to fail.Greg Clayton2013-05-031-1/+1
| | | | llvm-svn: 181069
* Adding test for non-API process attachAndrew Kaylor2013-05-031-0/+87
llvm-svn: 180977
OpenPOWER on IntegriCloud