summaryrefslogtreecommitdiffstats
path: root/lldb/test/lang/c/const_variables/TestConstVariables.py
Commit message (Collapse)AuthorAgeFilesLines
* Move lldb/test to lldb/packages/Python/lldbsuite/test.Zachary Turner2015-10-281-62/+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-17/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Fixed up TestConstVariables for Linux/FreeBSD, take 2.Todd Fiala2015-09-151-1/+9
| | | | | | | | | | | Marked XFAIL for: clang - all versions < 3.5. I verified the first version it passes on Linux is 3.5. clang - version 3.7 (verified this fails) clang - TOT/3.8 (verified this currently fails) Ideally we dig into why this started failing and (hopefully) get this passing again. llvm-svn: 247664
* Revert "Fixup XFAIL marking on TestConstVariables for clang version"Chaoren Lin2015-09-151-3/+1
| | | | | | | | | | | | | | | Summary: Linux with ToT clang (3.8) fails. This reverts commit r247633. Reviewers: tfiala Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D12868 llvm-svn: 247648
* Fixup XFAIL marking on TestConstVariables for clang versionTodd Fiala2015-09-141-1/+3
| | | | | | | | | | Linux/clang on clang 3.6+ is passing this test. As OS X was in a similar position, I'm guessing this was fixed by a recent compiler. Might work on 3.5/3.4, but it is definitely working on clang 3.6. I didn't break out FreeBSD since this appears to be related to a compiler fix. llvm-svn: 247633
* Correct XFAIL OS list after r247576Ed Maste2015-09-141-2/+2
| | | | | | | In ConstVariableTestCase::test_with_dwarf_and_run_command - the test fails with Clang (and presumably ICC) also on FreeBSD. llvm-svn: 247594
* Fix up bad compiler spec on ConstVariableTestCase; fixup two more OS X ↵Todd Fiala2015-09-141-1/+2
| | | | | | unexpected successes. llvm-svn: 247591
* Cleaned up a few unexpected successes on OS XTodd Fiala2015-09-141-2/+1
| | | | | | | | | TestCallStdStringFunction TestCallWithTimeout TestConstVariables TestClassTypes llvm-svn: 247576
* [Windows] XFAIL tests that depend on expression name lookup.Zachary Turner2015-08-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Name lookup doesn't work properly with Windows targets. This is most likely due to issues with name mangling, although there is at least one set of debug info related issues as well, since some of the name lookup requests appear to be failing on types rather than symbols. Specifically, this patch XFAILS the following set of tests: TestChar1632T.py TestRdar12991846.py TestConstVariables.py TestCallCPPFunction.py TestCallStopAndContinue.py TestCallUserDefinedFunction.py TestCModules.py TestCPPThis.py TestExprs2.py TestOverloadedFunctions.py TestRvalueReferences.py And fixing the underlying issue is tracked in http://llvm.org/pr24489 llvm-svn: 245338
* Reversed r238363, because the message is inconsistentSean Callanan2015-07-011-1/+1
| | | | | | with all the other assertion messages. llvm-svn: 241212
* [TestBase.runCmd] Better error message when runCmd fails.Siva Chandra2015-05-271-1/+1
| | | | | | | | | | | | | | | | | | | | | 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
* Converted TestConstVariables expected failure to @expectedFailureClang.Todd Fiala2014-02-281-2/+1
| | | | | | | | | TestConstVariables.py was disabled on Linux and marked as unconditional expected failure. This change removes the Linux disable and makes the expected failure conditional on using clang. The test runs fine on gcc-built lldb. llvm-svn: 202514
* 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
* Update break conditions test to have consistent behaviour on all test suite ↵Matt Kopec2013-07-311-1/+1
| | | | | | | | compilers. Also update comment in const variables test to reflect ICC status. llvm-svn: 187501
* 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
* Mark TestConstVariables as expected to fail due to radar 13314878 on darwin. ↵Greg Clayton2013-05-021-0/+2
| | | | | | The tests are already skipped on linux. llvm-svn: 180965
* Skipping TestConstVariables on Linux.Andrew Kaylor2013-03-061-1/+1
| | | | | | The test was marked as expectedFailureLinux, but now it passes with gcc and some versions of clang. Newer versions of clang introduce a failure due to bad DWARF information. llvm-svn: 176581
* Mark last known Linux failure as XFAIL to see if there's any other problems ↵Daniel Malea2013-02-221-0/+1
| | | | | | with buildbots. llvm-svn: 175917
* Fix a problem with the const_variables test case (another lldb bug remains)Daniel Malea2013-02-201-0/+2
| | | | | | | - make the test case step past the location where 'index' is initialized, otherwise its value cannot be printed (verified gcc 4.6/4.7 and recent clang) - "Couldn't materialize struct" error from LLDB still prevents this test case from passing llvm-svn: 175653
* Made the expression handle variables withSean Callanan2013-01-181-0/+66
DW_AT_const_value instead of a location. Also added a testcase covering "frame variable," "expr" using the IR interpreter, and "expr" using the LLVM JIT. <rdar://problem/12978195> llvm-svn: 172848
OpenPOWER on IntegriCloud