summaryrefslogtreecommitdiffstats
path: root/lldb/test/python_api/event
Commit message (Collapse)AuthorAgeFilesLines
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-283-339/+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
* Port the python api decorator to use test categoriesPavel Labath2015-10-261-3/+3
| | | | | | | | | | | | | | | | | | Summary: Per discussions on the mailing list, I have implemented a decorator which annotates individual test methods with categories. I have used this framework to replace the '-a' and '+a' command-line switches (now '-G pyapi' and '--skip-category pyapi') and the @python_api_test decorator (now @add_test_categories('pyapi')). The test suite now gives an error message suggesting the new options if the user specifies the deprecated +/-a switches. If the general direction is good, I will follow this up with other switches. Reviewers: tberghammer, tfiala, granata.enrico, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D14020 llvm-svn: 251277
* Add from __future__ import print_function everywhere.Zachary Turner2015-10-231-15/+17
| | | | | | | | | | | | | 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-57/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Marked TestEvents test as flakey on Linux.Todd Fiala2015-09-141-1/+1
| | | | | | | It's passing all the time for me (50/50), and was passing what looks like 9/10 times for the originator. llvm-svn: 247639
* XFAIL miscellaneous tests on windows.Zachary Turner2015-09-111-0/+1
| | | | | | llvm.org/pr24778 llvm-svn: 247460
* Fix typos.Bruce Mitchener2015-07-221-1/+1
| | | | | | | | | | | | Summary: Fix a bunch of typos. Reviewers: clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D11386 llvm-svn: 242856
* Un-enable TestEvents test on linuxPavel Labath2015-06-021-0/+2
| | | | | | Test still seems to fail about 1/10 runs. Skipping the test, but it a more greppable fashion. llvm-svn: 238826
* Enable TestEvents test on linuxPavel Labath2015-06-021-1/+0
| | | | | | | This test was very inconspicuosly skipped on linux, when it was crashing for local debugging. It seems to work fine with LLGS, so I'm enabling it. llvm-svn: 238816
* Add bug number for TestEventsTamas Berghammer2015-05-211-1/+1
| | | | llvm-svn: 237904
* XFAIL TestEvents on Linux bacuse it is flakyTamas Berghammer2015-05-211-0/+1
| | | | llvm-svn: 237888
* [TestEvents] Add a 'connected' state to include remote debugging.Siva Chandra2015-05-081-10/+20
| | | | | | | | | | | | | | Test Plan: dotest.py -p TestEvents Reviewers: vharron, chaoren Reviewed By: chaoren Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D9581 llvm-svn: 236800
* un-skipped a bunch of tests on LinuxVince Harron2015-05-041-2/+0
| | | | | | | | | Some have been marked as skipIfLinux for years. The seem to be passing so I've enabled them. Differential Revision: http://reviews.llvm.org/D9428 llvm-svn: 236403
* Many many test failures after some recent changes. The problem is ↵Greg Clayton2015-04-021-1/+1
| | | | | | | | | | | | | | | | 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
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-301-6/+4
| | | | | | | | | | | | | | | | 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
* [TestEvents] Replace expectedFailureLinux with skipIfLinuxSiva Chandra2014-12-191-2/+5
| | | | | | | | | | | | | | | | | | | | | Summary: If we do not mark them as skip, they are still executed, which in turn is leading to an assertion failure. The change also adds skipIfLinux to a testlet which was not previously marked with skipIfLinux. This is because running even that test let leads to an assertion failure. Test Plan: dotest.py -C clang -p TestEvents.py Reviewers: vharron Reviewed By: vharron Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D6715 llvm-svn: 224644
* Mark 9 lldb unit tests for ubuntu as XFAIL.Siva Chandra2014-11-221-0/+2
| | | | | | | | | | | | | | | | | | | | The following lldb unit tests fail check-lldb on ubuntu: TestDataFormatterStdMap.py TestDataFormatterStdVBool.py TestDataFormatterStdVector.py TestDataFormatterSynthVal.py TestEvents.py TestInitializerList.py TestMemoryHistory.py TestReportData.py TestValueVarUpdate.py These unit test failures are for non-core functionality. The intent is to reduce the check-lldb FAILS to core functionality FAILS and then circle back later and fix these FAILS at a later date. llvm-svn: 222608
* Temporarily disable test on FreeBSD that is assertingEd Maste2014-10-291-0/+1
| | | | | | llvm.org/pr21325 llvm-svn: 220871
* Fixed python API event test cases.Greg Clayton2014-10-171-39/+46
| | | | | | | | Issues were: 1 - It isn't good to have more than one listener for the process events, just supply a listener at launch instead of making a one then have the process broadcaster add a new listener 2 - run in async mode llvm-svn: 220113
* Correctly set the working directory when launching processes for both local ↵Greg Clayton2013-12-131-2/+2
| | | | | | and remote targets. llvm-svn: 197266
* 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 decorator to skip event testsDaniel Malea2012-11-231-2/+0
| | | | | | - hang resolved in r168503 llvm-svn: 168530
* Temporarily skip tests known to hang on LinuxDaniel Malea2012-11-191-0/+2
| | | | | | - opened bugzilla defects #14384 and #14385 llvm-svn: 168323
* Second batch of adding @dsym_test/@dwarf_test decorators to existing test cases.Johnny Chen2012-04-061-2/+8
| | | | | | | Plus some minor cleanup of test method names. Third and final batch is coming. llvm-svn: 154197
* A more succinct assertTrue.Johnny Chen2011-07-201-2/+1
| | | | llvm-svn: 135544
* Minor change; add an assertTrue stmt.Johnny Chen2011-07-201-0/+1
| | | | llvm-svn: 135542
* Passing in os.ctermid() as the arg for SBTarget.Launch(...) for stdin_path, ↵Johnny Chen2011-07-111-1/+1
| | | | | | | | | | | | stdout_path, and stderr_path is just wrong and resulted in the inferior's output getting mixed into the GDB remote communication's log file. Change all test cases to not pass os.ctermid() and either use SBTarget.LaunchSimple() or SBTarget.Launch() and pass None as stdin_path/stdout_path/srderr_path to use a pseudo terminal. rdar://problem/9716499 program output is getting mixed into the GDB remote communications llvm-svn: 134940
* o TestEvents.py:Johnny Chen2011-07-081-0/+87
| | | | | | | | | | | | | | | | Add a usage example of SBEvent APIs. o SBEvent.h and SBListener.h: Add method docstrings for SBEvent.h and SBListener.h, and example usage of SBEvent into the class docstring of SBEvent. o lldb.swig: Add typemap for SBEvent::SBEvent (uint32_t event, const char *cstr, uint32_t cstr_len) so that we can use, in Python, obj2 = lldb.SBEvent(0, "abc") to create an SBEvent. llvm-svn: 134766
* The extra burden for the Python API test case to assign its process object ↵Johnny Chen2011-06-151-12/+8
| | | | | | | | | to self.process in order to have its process cleaned up (terminated) upon tearDown is gone for good. Let's simplify a bunch of Python API test cases. llvm-svn: 133097
* Now that we have added a post-processing step for adding truth value testing toJohnny Chen2011-05-241-10/+10
| | | | | | | those lldb objects which implement the IsValid() method, let's change the rest of the test suite to use the more compact truth value testing pattern (the Python way). llvm-svn: 131970
* Convert the rest of the test suite to use the lldbutil.get_description() ↵Johnny Chen2011-04-231-5/+3
| | | | | | utility function. llvm-svn: 130041
* Converted to use SBProcess.LaunchSimple().Johnny Chen2011-04-191-2/+1
| | | | llvm-svn: 129789
* Modify test scripts to accomodate SBTarget.Launch() API change.Johnny Chen2011-02-031-5/+5
| | | | llvm-svn: 124828
* Deprecated old forms of SBTarget::Launch. There is not just one and noGreg Clayton2011-01-231-2/+4
| | | | | | SWIG renaming done to work around deprecated APIs. llvm-svn: 124075
* No need to pass an empty string as an arg or as an env string to the ↵Johnny Chen2010-12-221-2/+2
| | | | | | SBTarget.LaunchProcess() API. llvm-svn: 122450
* Fix some typos in the docstrings and also update the test method names.Johnny Chen2010-12-221-13/+12
| | | | llvm-svn: 122382
* Add test cases for registering a listener object with the broadcaster of a ↵Johnny Chen2010-12-221-16/+126
| | | | | | | | | process and waiting for two expected state changed events to arrive: "running" followed by "stopped". llvm-svn: 122380
* Rename the test methods to be more meaningful.Johnny Chen2010-12-211-8/+8
| | | | llvm-svn: 122352
* Set the debugger to asynchronous mode before using the Python API call to killJohnny Chen2010-12-211-2/+11
| | | | | | | the process. The custom thread started before this point is running in a loop waiting for events to come. llvm-svn: 122316
* Fix typo.Johnny Chen2010-12-211-1/+1
| | | | llvm-svn: 122306
* Added python_api/event/TestEvents.py to get the listener object associated ↵Johnny Chen2010-12-213-0/+154
with the debugger and to exercise some event APIs. llvm-svn: 122304
OpenPOWER on IntegriCloud