summaryrefslogtreecommitdiffstats
path: root/lldb/test/macosx
Commit message (Collapse)AuthorAgeFilesLines
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-2826-1097/+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-277-7/+7
| | | | llvm-svn: 251444
* Port the python api decorator to use test categoriesPavel Labath2015-10-264-4/+4
| | | | | | | | | | | | | | | | | | 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-237-7/+21
| | | | | | | | | | | | | 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-227-53/+16
| | | | | | | | | | | | | | | | | | | | | 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
* In r240466, when Greg added the jThreadsInfo packet, he accidentallyJason Molenda2015-10-152-1/+80
| | | | | | | | | | | | | | disabled the use of the jThreadGetExtendedInfo packet which is used to retrieve additional information about a thread, such as the QoS setting for that thread on darwin systems. Re-enable the use of the jThreadGetExtendedInfo packet, and add some quick tests to the TestQueues mac test case which will verify that we can retrieve the QoS names for these test threads. <rdar://problem/22925096> llvm-svn: 250364
* Expected fail this test and supplied the radar number that is tracking the fix.Greg Clayton2015-10-071-1/+2
| | | | llvm-svn: 249631
* Merge dwarf and dsym testsTamas Berghammer2015-09-307-94/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Reversed r238363, because the message is inconsistentSean Callanan2015-07-011-2/+2
| | | | | | with all the other assertion messages. llvm-svn: 241212
* Check before using platform specific attributes.Chaoren Lin2015-06-051-2/+4
| | | | | | | | | | | | Summary: `os.uname` in TestUniversal and `os.geteuid` in TestTerminal. Reviewers: clayborg, zturner Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D10202 llvm-svn: 239135
* [TestBase.runCmd] Better error message when runCmd fails.Siva Chandra2015-05-271-2/+2
| | | | | | | | | | | | | | | | | | | | | 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
* Replace sys.platform skips in tests with @skip decorators which check ↵Robert Flack2015-03-307-15/+15
| | | | | | | | | | | | | | | | 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
* Remove shell-globbing from all test makefiles.Zachary Turner2014-07-314-4/+4
| | | | llvm-svn: 214441
* Fixes a number of issue related to test portability on Windows.Zachary Turner2014-07-181-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | 99% of this CL is simply moving calls to "import pexpect" to a more narrow scope - i.e. the function that actually runs a particular test. This way the test suite can run on Windows, which doesn't have pexpect, and the individual tests that use pexpect can be disabled on a platform-specific basis. Additionally, this CL fixes a few other cases of non-portability. Notably, using "ps" to get the command line, and os.uname() to determine the architecture don't work on Windows. Finally, this also adds a stubbed out builder_win32 module. The full test suite runs correctly on Windows after this CL, although there is still some work remaining on the C++ side to fix one-shot script commands from LLDB (e.g. script print "foo"), which currently deadlock. Reviewed by: Todd Fiala Differential Revision: http://reviews.llvm.org/D4573 llvm-svn: 213343
* Add a new SBThread::SafeToCallFunctions API; this calls over toJason Molenda2014-05-133-0/+139
| | | | | | | | | | the SystemRuntime to check if a thread will have any problems performing an inferior function call so the driver can skip making that function call on that thread. Often the function call can be executed on another thread instead. <rdar://problem/16777874> llvm-svn: 208732
* Add a new SBThread::GetQueue() method to get the queue that is Jason Molenda2014-04-251-0/+1
| | | | | | | | | | currently associated with a given thread, on relevant targets. Change the queue detection code to verify that the queues associated with all live threads are included in the list. <rdar://problem/16411314> llvm-svn: 207160
* Fixed up intermittently failing tests to skip on Linux.Todd Fiala2014-03-251-0/+1
| | | | | | | | | | | Also added 'import sys' on some tests that are using non-standard unittest2.skipUnless blocks with code that is intended to do things that we have more specializes @* attributes for. These skip conditions were failing to execute due to missing import, causing darwin-only tests to run on Linux regardless. Will file a bug for that separately. llvm-svn: 204747
* Refactor the Queues test case a little based on feedback from Jim.Jason Molenda2014-03-131-59/+135
| | | | | | Add queues tests for when libBacktraceRecording is absent. llvm-svn: 203864
* Also check if the queues are serial or concurrent.Jason Molenda2014-03-131-1/+7
| | | | llvm-svn: 203755
* Add a quick test case for some of the queues debugging support.Jason Molenda2014-03-133-0/+253
| | | | | | | It should only run on Darwin systems, and only when a couple of libraries are available. llvm-svn: 203754
* Change the name of the test class for this test (was copy/paste value...)Jim Ingham2014-01-141-1/+1
| | | | llvm-svn: 199251
* Remove a compilation warning in the test case main.c file.Jim Ingham2014-01-141-1/+1
| | | | llvm-svn: 199243
* This is a macosx specific test case for stepping & setting breakpoints on ↵Jim Ingham2014-01-136-0/+190
| | | | | | | | | | indirect and re-exported symbols. I don't know if Linux has the latter, if it does, we could probably make this a generic test. Somebody who knows how to make these gadgets on Linux can maybe take a look... llvm-svn: 199134
* Correctly set the working directory when launching processes for both local ↵Greg Clayton2013-12-132-2/+2
| | | | | | and remote targets. llvm-svn: 197266
* Massive test suite cleanup to stop everyone from manually having to compute ↵Greg Clayton2013-12-104-4/+4
| | | | | | | | | | "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
* merge lldb-platform-work branch (and assorted fixes) into trunkDaniel Malea2013-08-261-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Summary: This merge brings in the improved 'platform' command that knows how to interface with remote machines; that is, query OS/kernel information, push and pull files, run shell commands, etc... and implementation for the new communication packets that back that interface, at least on Darwin based operating systems via the POSIXPlatform class. Linux support is coming soon. Verified the test suite runs cleanly on Linux (x86_64), build OK on Mac OS X Mountain Lion. Additional improvements (not in the source SVN branch 'lldb-platform-work'): - cmake build scripts for lldb-platform - cleanup test suite - documentation stub for qPlatform_RunCommand - use log class instead of printf() directly - reverted work-in-progress-looking changes from test/types/TestAbstract.py that work towards running the test suite remotely. - add new logging category 'platform' Reviewers: Matt Kopec, Greg Clayton Review: http://llvm-reviews.chandlerc.com/D1493 llvm-svn: 189295
* A new test case which adds a dSYM to an executable mid-debug sessionJason Molenda2013-08-153-0/+65
| | | | | | | where the executable has been slid. This detects the regression fixed in r188289. llvm-svn: 188443
* Add missing -Xlinker to order test.Stefanus Du Toit2013-07-301-1/+1
| | | | | | | Both the parameter itself and the argument to the parameter must be prefixed with -Xlinker so that they are passed properly. llvm-svn: 187432
* Fix all the test case breakages caused by folks writing tests all over the ↵Jim Ingham2012-09-221-8/+3
| | | | | | | | place that depended explicitly on the output of "break set". Please don't do this sort of thing!!!!! llvm-svn: 164433
* <rdar://problem/11358639>Greg Clayton2012-05-081-1/+1
| | | | | | | | Switch over to the "*-apple-macosx" for desktop and "*-apple-ios" for iOS triples. Also make the selection process for auto selecting platforms based off of an arch much better. llvm-svn: 156354
* Remove the expectedFailure decorator as the bug has been fixed.Johnny Chen2012-04-211-1/+0
| | | | llvm-svn: 155264
* Second batch of adding @dsym_test/@dwarf_test decorators to existing test cases.Johnny Chen2012-04-061-0/+2
| | | | | | | Plus some minor cleanup of test method names. Third and final batch is coming. llvm-svn: 154197
* Add a Test case to make sure that __apple_types section does get produced by ↵Johnny Chen2012-04-031-3/+22
| | | | | | | | dsymutil. This is supposed to succeed even with rdar://problem/11166975. llvm-svn: 153919
* Add some more debug prints and retrieve the debug subsections from the DWARF ↵Johnny Chen2012-04-031-6/+14
| | | | | | section. llvm-svn: 153915
* Add testcase that verifies that __apple_types is a valid section in a .o ↵Johnny Chen2012-04-023-0/+93
| | | | | | | | file generated by clang. rdar://problem/11167268 llvm-svn: 153891
* Modify a couple of Makefiles to use clang instead of gcc, since gcc is being ↵Johnny Chen2012-01-121-4/+1
| | | | | | deprecated. llvm-svn: 148071
* Patches for running some of the Linux tests from Dawn, thanks!Johnny Chen2011-12-221-0/+1
| | | | | | With some minor modification from me. llvm-svn: 147160
* Add a simple test case to exercise the ↵Johnny Chen2011-08-131-0/+19
| | | | | | SBDebugger.CreateTargetWithFileAndTargetTriple() API. llvm-svn: 137544
* Modify the skipUnless() logic to work for OSX Lion.Johnny Chen2011-08-131-1/+1
| | | | llvm-svn: 137542
* Move top level test dirs platform and inferior-crashing to reside under ↵Johnny Chen2011-06-275-0/+117
| | | | | | functionalities and order to reside under macosx. llvm-svn: 133919
* Now that we have added a post-processing step for adding truth value testing toJohnny Chen2011-05-241-2/+2
| | | | | | | 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
* Add test scenario to verify 'eax' register is available when launching the ↵Johnny Chen2011-05-081-0/+11
| | | | | | | | | | i386 slice of a universal binary and 'rax' register is available when launching the x86_64 slice. rdar://problem/9403437 llvm-svn: 131069
* Add new radar info for failed test.Johnny Chen2011-02-081-1/+1
| | | | llvm-svn: 125100
* Make the assertion message about 32-bit process address byte size more clear.Johnny Chen2011-02-081-2/+5
| | | | llvm-svn: 125099
* Parametrize make variable CC to also test with clang.Johnny Chen2011-02-031-4/+9
| | | | llvm-svn: 124764
* Remove @expectedFailure decorator as the bug has been fixed.Johnny Chen2010-12-011-1/+0
| | | | llvm-svn: 120624
* Add @expectedFailure decorator for a known bug:Johnny Chen2010-12-011-0/+2
| | | | | | rdar://problem/8689814 test failure: test/macosx/universal (the i386 slice does not break?) llvm-svn: 120505
* Make the specification of relative directory more robust.Johnny Chen2010-11-091-1/+1
| | | | llvm-svn: 118511
* Make calling the super class's setUp() method less fragile.Johnny Chen2010-10-141-1/+2
| | | | llvm-svn: 116490
* Avoid using hardcoded line number to break on. Use the line_number() utilityJohnny Chen2010-10-122-5/+14
| | | | | | function to get the line number to break on during setUp(). llvm-svn: 116356
OpenPOWER on IntegriCloud