summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite
Commit message (Collapse)AuthorAgeFilesLines
* enable timeout/exceptional exit support for xUnit formatterTodd Fiala2015-12-093-2/+97
| | | | | | | Also adds enable.py/disable.py script to simplify turning on and off the issue_verification tests helpful for testing a results formatter. llvm-svn: 255161
* Remove the -P option from dotest.pyZachary Turner2015-12-094-21/+0
| | | | | | | | This was an option to display a graphical progress bar. Nobody is using this, and it doesn't work correctly anyway with the new result formatter. llvm-svn: 255153
* Delete the -n command line option from dotest.py.Zachary Turner2015-12-093-19/+7
| | | | | | | This removes the option to not print some one time version and diagnostic information when running the test suite. llvm-svn: 255152
* Remove the -i command line option from dotest.py.Zachary Turner2015-12-093-11/+0
| | | | | | | This is part of a larger effort to remove unused command line options from dotest.py. llvm-svn: 255151
* Delete the -F command line option from dotest.py.Zachary Turner2015-12-093-9/+0
| | | | | | | | This removes the failfast command line option as part of an effort to simplify dotest and remove unused command line options. You can still Ctrl+C any time you want to exit early. llvm-svn: 255150
* Remove -k command line option from dotest.py.Zachary Turner2015-12-095-97/+0
| | | | | | This is part of an effort to remove unused command line options. llvm-svn: 255143
* Remove -e option from dotest.py.Zachary Turner2015-12-097-27/+8
| | | | | | | This is part of an effort to clean up dotest command line options that are no longer used. llvm-svn: 255142
* Remove -libcxx option from dotest.pyZachary Turner2015-12-092-4/+0
| | | | | | | Nobody was using this, and plus it can be achieved just as well by using -E to set an environment variable. llvm-svn: 255141
* Move XunitFormatter into its own xunit_formatter.py file.Todd Fiala2015-12-092-483/+505
| | | | llvm-svn: 255139
* Fix new summary to include exceptional exit count in determining exit valueTodd Fiala2015-12-092-14/+35
| | | | | | | | | | | | The main dotest.py should exit with a system return code of 1 on any issue. This change fixes a place where I omitted counting the exceptional exit value to determine if we should return 1 when using the new summary results. This change also puts a banner around the Issue Details section that comes before the Test Result Summary. llvm-svn: 255138
* Disable the issue verification tests.Todd Fiala2015-12-093-0/+0
| | | | llvm-svn: 255134
* create 3 issues for testbots: FAIL, ERROR (exceptional), and TIMEOUTTodd Fiala2015-12-094-0/+66
| | | | | | | | | | | | | This change is a trial balloon to verify that the default test summary output sends the right output for the buildbot issue detection script. The effect of this change will be reverted after verifying the testbot behavior. This change will not stay in as is and will knowingly create noise, see this thread: http://lists.llvm.org/pipermail/lldb-dev/2015-December/009048.html llvm-svn: 255131
* Turn on new test summary results by default.Todd Fiala2015-12-092-2/+9
| | | | llvm-svn: 255130
* Correctly XFAIL TestReturnValuePavel Labath2015-12-091-1/+1
| | | | | | android is not an "os", use the target triple to match it. llvm-svn: 255118
* XFAIL TestReturnValue for remote Windows->Android testsPavel Labath2015-12-092-1/+4
| | | | | | this also adds the ability to match the host platform to the expectedFailureAll decorator. llvm-svn: 255105
* Fix a cleanup error in TestPlatformProcessConnect.pyTamas Berghammer2015-12-091-1/+1
| | | | llvm-svn: 255104
* wire timeouts and exceptional inferior process exits through the test event ↵Todd Fiala2015-12-095-54/+420
| | | | | | | | | | | | | | | | | | | | | | | system The results formatter system is now fed timeouts and exceptional process exits (i.e. inferior dotest.py process that exited by signal on POSIX systems). If a timeout or exceptional exit happens while a test method is running on the worker queue, the timeout or exceptional exit is charged and reported against that test method. Otherwise, if no test method was running at the time of the timeout or exceptional exit, only the test filename will be reported as the TIMEOUT or ERROR. Implements: https://llvm.org/bugs/show_bug.cgi?id=24830 https://llvm.org/bugs/show_bug.cgi?id=25703 In support of: https://llvm.org/bugs/show_bug.cgi?id=25450 llvm-svn: 255097
* Remove the -c option from dotest.py.Zachary Turner2015-12-086-164/+6
| | | | | | | | | | This seems to be a legacy relic from days gone by where the remote test suite runner operated completely differently than it does today. git blames and comments traced this functionality back to about 2012, and nobody seems to know anything about it now. llvm-svn: 255060
* Remove the -X option from dotest.pyZachary Turner2015-12-083-10/+3
| | | | | | | | This removes the option to exclude a single directory. This is part of an effort to remove unused options and cleanup the interface to the test suite. llvm-svn: 255048
* Remove the -g option from dotest.pyZachary Turner2015-12-083-11/+1
| | | | | | | | This removes the non-exclusive filterspec option as part of an effort to remove unused / deprecated command line options from dotest. llvm-svn: 255041
* Remove the -b option from dotest.pyZachary Turner2015-12-085-49/+0
| | | | | | | This removes the blacklist option as part of an effort to remove unused / unmaintained command line options from the test suite. llvm-svn: 255040
* Remove +b option from dotest.pyZachary Turner2015-12-084-22/+1
| | | | llvm-svn: 255037
* Remove the -D option from dotest.py.Zachary Turner2015-12-083-9/+0
| | | | | | | This removes the option to dump Python sys.path variable as part of an effort to remove unused options. llvm-svn: 255035
* flip on executable bit on test runner testsTodd Fiala2015-12-082-0/+0
| | | | llvm-svn: 255025
* Modify "platform connect" to connect to processes as wellTamas Berghammer2015-12-085-17/+87
| | | | | | | | | | | | | | | | | | | | | | | | The standard remote debugging workflow with gdb is to start the application on the remote host under gdbserver (e.g.: gdbserver :5039 a.out) and then connect to it with gdb. The same workflow is supported by debugserver/lldb-gdbserver with a very similar syntax but to access all features of lldb we need to be connected also to an lldb-platform instance running on the target. Before this change this had to be done manually with starting a separate lldb-platform on the target machine and then connecting to it with lldb before connecting to the process. This change modifies the behavior of "platform connect" with automatically connecting to the process instance if it was started by the remote platform. With this command replacing gdbserver in a gdb based worflow is usually as simple as replacing the command to execute gdbserver with executing lldb-platform. Differential revision: http://reviews.llvm.org/D14952 llvm-svn: 255016
* Add a new option to Platform::LoadImage to install the imageTamas Berghammer2015-12-081-8/+2
| | | | | | | | | | | | | | | | | | | | | This change introduce 3 different working mode for Platform::LoadImage depending on the file specs specified. * If only a remote file is specified then the remote file is loaded on the target (same behavior as before) * If only a local file is specified then the local file is installed to the current working directory and then loaded from there. * If both local and remote file is specified then the local file is installed to the specified location and then loaded from there. The same options are exposed on the SB API with a new method LoadImage method while the old signature presers its meaning. On the command line the installation of the shared library can be specified with the "--install" option of "process load". Differential revision: http://reviews.llvm.org/D15152 llvm-svn: 255014
* Fixup dotest.py on mac for the configuration packagePavel Labath2015-12-082-3/+3
| | | | llvm-svn: 255013
* Fixup dotest.py after the configuration package introductionPavel Labath2015-12-081-1/+1
| | | | llvm-svn: 255009
* Move LLDBTestResult class to its own module.Zachary Turner2015-12-083-231/+259
| | | | llvm-svn: 254983
* Get rid of global variables in dotest.pyZachary Turner2015-12-0821-721/+560
| | | | | | | | | | | | | | | | | | | | | | | | | | This moves all the global variables into a separate module called `configuration`. This has a number of advantages: 1. Configuration data is centrally maintained so it's easy to get a high level overview of what configuration data the test suite makes use of. 2. The method of sharing configuration data among different parts of the test suite becomes standardized. Previously we would put some things into the `lldb` module, some things into the `lldbtest_config` module, and some things would not get shared. Now everything is shared through one module and is available to the entire test suite. 3. It opens the door to moving some of the initialization code into the `configuration` module, simplifying the implementation of `dotest.py`. There are a few stragglers that didn't get converted over to using the `configuration` module in this patch, because it would have grown the size of the patch unnecessarily. This includes everything currently in the `lldbtest_config` module, as well as the `lldb.remote_platform` variable. We can address these in the future. llvm-svn: 254982
* Trying to submit 254476 one more time. This implement -gmodule debugging ↵Greg Clayton2015-12-081-2/+2
| | | | | | | | | | | | | | support. It was previously reverted due to issues that showed up only on linux. I was able to reproduce these issues and fix the underlying cause. So this is the same patch as 254476 with the following two fixes: - Fix not trying to complete classes that don't have external sources - Fix ClangASTSource::CompleteType() to check the decl context of types that it finds by basename to ensure we don't complete a type "S" with a type like "std::S". Before this fix ClangASTSource::CompleteType() would accept _any_ type that had a matching basename and copy it into the other type. <rdar://problem/22992457> llvm-svn: 254980
* Refactor ResultsFormatter creation into result_formatter.Todd Fiala2015-12-082-73/+133
| | | | | | | | | This cleans up dotest.py and is a pre-step for getting the test inferior runner to send post-inferior run events to the events collector, as this code needs to be accessed from within dosep.py. llvm-svn: 254979
* Add NetBSD in platform specific logging of the specified category in ↵Kamil Rytarowski2015-12-071-0/+3
| | | | | | | | | | | | | | RegisterCommandsTestCase() Summary: NetBSD soon will reuse this feature while running tests. Reviewers: emaste, tfiala, clayborg Subscribers: lldb-commits, joerg Differential Revision: http://reviews.llvm.org/D15263 llvm-svn: 254949
* Add initial NetBSD support in lldbsuite/test/lldbtest.pyKamil Rytarowski2015-12-071-5/+21
| | | | | | | | | | | | | | | | | | | | | | | | Summary: Add new functions: - expectedFailureNetBSD() - expectedFlakeyNetBSD() - skipIfNetBSD() Add new NetBSD entry in: - getPlatform() - getHostPlatform() Assume that libc++ is installed and use the GNU toolchain Reviewers: joerg, emaste, tfiala, clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D15262 llvm-svn: 254948
* Return gmake as the default name for GNU make on NetBSDKamil Rytarowski2015-12-071-1/+1
| | | | | | | | | | | | | | | Summary: The base make(1) on NetBSD is BSD make. In the default installation of NetBSD GNU make comes via pkgsrc under the gmake name. Reviewers: emaste, tfiala, clayborg Subscribers: joerg, lldb-commits Differential Revision: http://reviews.llvm.org/D15261 llvm-svn: 254947
* Rename test_results.py to result_formatter.py.Zachary Turner2015-12-075-19/+20
| | | | | | | | There is already a class called LLDBTestResults which I would like to move into a separate file, but the most appropriate filename was taken. llvm-svn: 254946
* getwd(3) with NULL pointer extension is supported on NetBSDKamil Rytarowski2015-12-071-2/+2
| | | | | | | | | | | | | | | | | | | | | | Summary: The getwd() and getcwd() functions conform to IEEE Std 1003.1-1990 (POSIX.1). The IEEE Std 1003.1-2004 (POSIX.1) revision marked getwd() as legacy and recommended the use of getcwd() instead. The IEEE Std 1003.1-2008 (``POSIX.1'') revision removed getwd() from the specification. The ability to specify a NULL pointer and have getcwd() allocate memory as necessary is an extension. The getwd() function appeared in 4.0BSD. Reviewers: emaste, tfiala, clayborg Subscribers: lldb-commits, joerg Differential Revision: http://reviews.llvm.org/D15260 llvm-svn: 254944
* Allow variable names to be quoted with -var-list-childrenChuck Ries2015-12-071-0/+3
| | | | | | | | Allow both '-var-list-children var0' and '-var-list-children "var0"' to be used with the -var-list-children command. GDB MI allows for this and it is necessary if the variable name contains spaces, such as var5.std::_Vector_base<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<cahr> > > >. Differential Revision: http://reviews.llvm.org/D15168 llvm-svn: 254941
* Recommit "Fix race during process interruption"Pavel Labath2015-12-072-3/+5
| | | | | | | | This is a resubmit of r254403, see that commit's message for context. This fixes an issue in the original commit, where we would incorrectly interrupt the process if the interrupt request came just as we were about to send the stopped event to the public. llvm-svn: 254902
* Make TestThreadStates more stablePavel Labath2015-12-071-25/+11
| | | | | | | | | | | | | | | | | | | | | Summary: Because of the large number of XFAILs TestThreadStates has decayed quite a bit. This commit does the following: - removes the "breakpoint list" expectations. Most tests have been failing on this, because the command output changed quite a while back. I remove it, because run_break_set_by_file_and_line already does a decent amount of checking - fixup test_state_after_expression: this was calling the wrong function by mistake. As now the function actually tests something (which we know is broken), I needed to XFAIL it as well. - replaces the sleep() with a proper wait-for-event functionality in parts which use async mode, to stabilize the one function that actually tests something. Reviewers: clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D15233 llvm-svn: 254901
* Added lldbsuite.lldb_test_root, switched formatter to use it.Todd Fiala2015-12-072-5/+10
| | | | llvm-svn: 254894
* [LLDB][MIPS] Marking some expected failuresMohit K. Bhakkad2015-12-072-11/+17
| | | | | | | | Reviewers: clayborg, zturner. Subscribers: jaydeep, bhushan, sagar, nitesh.jain, tberghammer,lldb-commits. Differential Revision: http://reviews.llvm.org/D14944 llvm-svn: 254892
* Moved total test count and rerun count into summary counts.Todd Fiala2015-12-071-8/+22
| | | | llvm-svn: 254891
* Move test summary counts to end; simplify issue detail lineTodd Fiala2015-12-071-6/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Test summary counts now show at the end, with issue details above. Issue details now print "ISSUE_TYPE: test method (relative path)". Relative paths are relative to the packages/Python/lldbsuite/test directory. Sample output: test/dotest.py --executable `pwd`/build/Debug/lldb --results-formatter lldbsuite.test.basic_results_formatter.BasicResultsFormatter --threads 12 Testing: 415 test suites, 12 threads 415 out of 415 test suites processed - TestLldbGdbServer.py Test Results Total Test Methods Run (excluding reruns): 2470 Test Method rerun count: 0 Details: UNEXPECTED SUCCESS: test_symbol_name_dsym (functionalities/completion/TestCompletion.py) UNEXPECTED SUCCESS: test_symbol_name_dwarf (functionalities/completion/TestCompletion.py) =================== Test Result Summary =================== Success: 1329 Expected Failure: 79 Failure: 0 Error: 0 Unexpected Success: 2 Skip: 1060 llvm-svn: 254890
* Define new builder_netbsdKamil Rytarowski2015-12-052-0/+6
| | | | | | | | | | | | Summary: This is used in tests. Reviewers: emaste, tfiala, clayborg Subscribers: zturner, lldb-commits, joerg Differential Revision: http://reviews.llvm.org/D15065 llvm-svn: 254853
* [LLDB][MIPS] Fix TestConstVariables.pySagar Thakur2015-12-051-0/+1
| | | | | | | | | | | Patch by Nitesh Jain. Summary: There is no debug information generated for variable index with –O3 optimization flag. The DW_AT_location tag in DWARF debug_info section is empty. Reviewers: ovyalov, clayborg Subscribers: lldb-commits, mohit.bhakkad, sagar, bhushan, jaydeep Differential: http://reviews.llvm.org/D15224 llvm-svn: 254850
* Make TestThreadSpecificBreakpoint.py more focused.Zachary Turner2015-12-045-53/+143
| | | | | | | | | | | | | | | | This test would fail before if conditional breakpoints weren't working correctly, and the nature of the test (spinning up 10 threads, etc) opens the door to raciness. This patch vastly simplifies the test, removes the need for relying on conditional expression evaluation, and as a result makes the correctness of the test vastly easier to reason about and reduces flakiness. Differential Revision: http://reviews.llvm.org/D15241 Reviewed By: Jim Ingham llvm-svn: 254792
* Add a similar benchmark for our std::map performanceEnrico Granata2015-12-043-0/+75
| | | | llvm-svn: 254779
* Fix an issue where all tests marked with skip_if_callable would be skipped ↵Enrico Granata2015-12-041-4/+5
| | | | | | regardless of the actual callable llvm-svn: 254758
* Add a benchmark that validates how much time LLDB spends trying to fully ↵Enrico Granata2015-12-043-0/+75
| | | | | | | | print a fairly large std::list<T> This is meant to help me track optimizations to the libc++ std::list data formatter llvm-svn: 254755
OpenPOWER on IntegriCloud