summaryrefslogtreecommitdiffstats
path: root/lldb/test
Commit message (Collapse)AuthorAgeFilesLines
...
* test runner: Unix systems now put inferior dotest in its own process group.Todd Fiala2015-09-221-1/+2
| | | | | | | This increases isolation as it relates to signal handling between parent and children. llvm-svn: 248282
* Remove expectedFailureFreeBSD from passing testsEd Maste2015-09-222-2/+0
| | | | | | | | | These two tests are skipped on Linux with a comment that the behaviour is as expected, but they are consistently passing on FreeBSD now. llvm.org/pr15989 llvm-svn: 248271
* Remove expectedFailureFreeBSD from passing testEd Maste2015-09-221-1/+0
| | | | | | | | | HelloWorldTestCase::test_with_dwarf_and_process_launch_api passes consistently for me and for John Wolfe. llvm.org/pr21620 llvm-svn: 248269
* xUnit test formatter: add options for ignoring skipped testsTodd Fiala2015-09-221-1/+68
| | | | | | | | | | | | | Skipped tests can be dropped from xUnit reports if either the name or the skip reason matches one of a given set of regular expression patterns (via re.search(), not re.match()). New formatter option for the xunit formatter: --ignore-skip-matching-reason and --ignore-skip-matching-name Both are results-formatter options. llvm-svn: 248247
* Remove expectedFailureFreeBSD from passing test_expr_null_with_dwarfEd Maste2015-09-221-1/+0
| | | | | | llvm.org/pr21550 llvm-svn: 248236
* Split the curses stuff out into a separate file so that we can import curses ↵Greg Clayton2015-09-222-129/+185
| | | | | | | | | | and lldbcurses at the module level. Added key press handling and a first responder system and the ability for windows that can be first responders to be selected and have key presses routed to the first resonder, delegates and also travel up the parent chain. Remove the temp file that was being created. llvm-svn: 248232
* test framework: parallel test runner sends terminate to formatter before ↵Todd Fiala2015-09-223-4/+23
| | | | | | | | | | | | printing to stdout The parallel test runner now sends the terminate event to the formatter (if there is one) after the parallel test runs but before dumping anything to stdout/stderr at the end of the run. This allows the existing stdout/stderr summary reporting to co-exist nicely with a formatter like the test_results.Curses that otherwise clobbers the screen. llvm-svn: 248228
* Fixed up the curses test results formatter to:Greg Clayton2015-09-212-62/+66
| | | | | | | | | - rename "Failures" window to "Completed Tests" - Remove the extra lock that I incorrectly added to the ResultsFormatter as it already had one - Init the curses GUI with the right number of jobs when handling the "intialize" event - tear down the curses GUI when tests complete llvm-svn: 248179
* XFAIL TestConnectRemote.py on FreeBSDEd Maste2015-09-211-0/+1
| | | | | | | | | | Test fails with: error: Process 1 was reported after connecting to 'connect://localhost:42922', but no stop reply packet was received llvm.org/pr24896 llvm-svn: 248157
* For now skip go tests that trigger assertion failures on FreeBSDEd Maste2015-09-212-0/+2
| | | | | | llvm.org/pr24895 llvm-svn: 248155
* test framework: ignore sighupsTodd Fiala2015-09-211-0/+5
| | | | | | | | | | | | | On OS X, we're occasionally seeing sighups come in to what looks like the whole test runner process group (all the multiprocessing workers and the main process). It's not due to a lost console. This change has the main parallel test runner process and the child worker processes ignore sighup. Covers: https://llvm.org/bugs/show_bug.cgi?id=24846 llvm-svn: 248141
* Fix Linux bot.Chaoren Lin2015-09-191-1/+2
| | | | llvm-svn: 248075
* Added a curses based way to see the test suite running. Works only where ↵Greg Clayton2015-09-193-17/+413
| | | | | | | | curses is implemented. Try it out with: ./dotest.py --results-formatter=test_results.Curses --results-file=/dev/stdout llvm-svn: 248072
* test events: added optional value type to extra event key/val pairsTodd Fiala2015-09-183-4/+11
| | | | | | | | | | | | | The test events had worker indexes coming across as strings. I want them to be ints. worker_index now comes across as an int in the dicationary. The optional type can be specified with: --event-add-entries key=val[:type][,key2=val2[:type2]...] The type piece may be 'int' at this time. That is all. Otherwise it will be a string. llvm-svn: 248066
* test events: add test_filename to all test-related events.Todd Fiala2015-09-181-0/+1
| | | | | | | The test_filename is the full path to the TestCase class's implementation file. llvm-svn: 248060
* test events: announce worker count in new initialize eventTodd Fiala2015-09-184-109/+103
| | | | | | | See the following for details: http://reviews.llvm.org/D12987 llvm-svn: 248059
* On Linux, if you can't actually locate the libc++ install, do not attempt to ↵Enrico Granata2015-09-181-4/+9
| | | | | | | | | use it The failure mode when one gets this wrong is quite gnarly to then walk oneself out of, and if you can't actually find the library, trying to build against it is fairly pointless anyway This + my previous skip_if_library_missing change should make running the libc++ tests on a Linux machine without it much more seamless llvm-svn: 248057
* Adds parallel work queue index to test events, stdout/stderr results support.Todd Fiala2015-09-184-47/+185
| | | | | | See http://reviews.llvm.org/D12983 for details. llvm-svn: 248036
* Make libc++ tests skip themselves if libc++ is not actually loaded in the targetEnrico Granata2015-09-1812-1/+59
| | | | llvm-svn: 248028
* xUnit test output: implemented proper xml escapingTodd Fiala2015-09-181-18/+53
| | | | | | | | | | | | | | | Now does proper Unicode code region scanning for invalid XML characters. Strips out XML-invalid characters. Does this for: failure result: message, backtrace error result: message, backtrace skipped test: skip reason pexpect timeouts were still generating characters that would break XML readers (correctly so). llvm-svn: 247998
* xunit output: add backtraces; limit attributeTodd Fiala2015-09-181-4/+33
| | | | | | | | | | | | | | | | When pexpect errors occurred, the <error>/<failure> element's message attribute could get too long and contain invalid characters for xml attributes, even when quoted. Particularly for pexpect failures. Now <error> and <failure> entries truncate the message attribute to contain the first line of the message. <error> and <failure> blocks now contain both the complete message and the backtrace (finally!) in the text body of the error/failure element. llvm-svn: 247973
* Fixed test runner output for Jenkins xUnit publishTodd Fiala2015-09-181-1/+2
| | | | | | | | | The Jenkins JUnit publisher handled our output, but the Jenkins xUnit plugin's JUnit support did not like that we didn't have a <testsuites> element wrapping everything. They both work with this fix. llvm-svn: 247962
* Get the process ID from a minidump.Adrian McCarthy2015-09-171-1/+1
| | | | llvm-svn: 247939
* Fix TestMiSymbol for gcc-4.9 test.Chaoren Lin2015-09-171-1/+1
| | | | llvm-svn: 247914
* [lldb-mi] Fix the handling of files in -data-info-line and -symbol-list-lines.Dawn Perchik2015-09-176-3/+121
| | | | | | | | | | | | | This fixes -data-info-line and -symbol-list-lines to parse the filename and line correctly when line entries don't have the optional column number and the filename contains a Windows drive letter. It also fixes -symbol-list-lines when code from header files is generated. Reviewed by: abidh, ki.stfu Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D12115 llvm-svn: 247899
* XFAIL step after crash tests on android-aarch64 API 21Tamas Berghammer2015-09-172-0/+2
| | | | | | | Android-aarch64 for API21 uses sa_restore to return from a signal handler what have no eh_frame specified. llvm-svn: 247879
* Remove XTIMEOUT from TestAttachDenied on linuxPavel Labath2015-09-171-1/+0
| | | | llvm-svn: 247877
* Add the ability for formatter categories to be bound to one or more languagesEnrico Granata2015-09-172-9/+7
| | | | | | What that does is it restricts formatters in those categories to only match to types coming from "compatible" source languages llvm-svn: 247872
* XFAIL TestCppNsImport for gcc-4.9 inclusive.Chaoren Lin2015-09-161-1/+1
| | | | llvm-svn: 247863
* Fix Makefile for Windows to Android tests.Chaoren Lin2015-09-161-5/+6
| | | | | | | | | | Reviewers: zturner Subscribers: tberghammer, lldb-commits, danalbert Differential Revision: http://reviews.llvm.org/D12909 llvm-svn: 247857
* XFAIL TestCppNsImport for gcc-4.9.Chaoren Lin2015-09-161-0/+1
| | | | | | Works for gcc-4.8. A bug in gcc perhaps. llvm-svn: 247855
* Add an OperatingSystem plugin to support goroutinesRyan Brown2015-09-162-0/+176
| | | | | | | | | | The Go runtime schedules user level threads (goroutines) across real threads. This adds an OS plugin to create memory threads for goroutines. It supports the 1.4 and 1.5 go runtime. Differential Revision: http://reviews.llvm.org/D5871 llvm-svn: 247852
* Add using directives to the clang::DeclContext and fix decls for variables ↵Paul Herman2015-09-161-6/+9
| | | | | | | | | | | | | | inside namespaces Summary: Supports the parsing of the "using namespace XXX" and "using XXX::XXX" directives. Added ambiguity errors when it two decls with the same name are encountered (see comments in TestCppNsImport). Fixes using directives being duplicated for anonymous namespaces. Fixes GetDeclForUID for specification DIEs. Reviewers: sivachandra, chaoren, clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D12897 llvm-svn: 247836
* Remove XFAIL from TestCppNsImport.Zachary Turner2015-09-161-2/+0
| | | | | | This test seems to be working now, probably due to r244764. llvm-svn: 247830
* Add first tests for mini-dump debugging.Adrian McCarthy2015-09-164-0/+77
| | | | | | Differential Revision: http://reviews.llvm.org/D12888 llvm-svn: 247829
* Last set of XFAILs for Windows.Zachary Turner2015-09-168-0/+10
| | | | llvm-svn: 247825
* Decorate flaky FreeBSD testEd Maste2015-09-161-0/+1
| | | | | | | | | | | | | ExprCommandWithTimeoutsTestCase::expectedFailureFreeBSD had an expectedFailureFreeBSD decorator, removed in r247799. It had been flakey on the FreeBSD buildbot but passed locally. John Wolfe has since observed a local failure, so add expectedFlakeyFreeBSD until we can investigate and likely increase the timeout in the test. llvm.org/pr19605 (FreeBSD) llvm.org/pr20275 (equivalent Linux issue) llvm-svn: 247822
* Upgrading TestCreateDuringInstructionStep from XFLAKY to XFAIL on android armPavel Labath2015-09-161-1/+1
| | | | | | the test is very often failing two times in a row, causing noise on the buildbots. llvm-svn: 247805
* Remove expectedFailureFreeBSD from passing watchpoint testsEd Maste2015-09-163-3/+0
| | | | | | llvm.org/pr18832 llvm-svn: 247801
* Remove expectedFailureFreeBSD from passing testEd Maste2015-09-161-1/+0
| | | | | | | | ExprCommandCallUserDefinedFunction::test_with_dwarf llvm.org/pr21142 llvm-svn: 247800
* Remove expectedFailureFreeBSD from passing testEd Maste2015-09-161-1/+0
| | | | | | | | | | | | | ExprCommandWithTimeoutsTestCase::expectedFailureFreeBSD This test passes locally but was marked XFAIL due to failures on the FreeBSD buildbot. That buildbot has been retired as it was overloaded, and we will investigate again if this fails once a new buildbot is in place. llvm.org/pr19605 llvm-svn: 247799
* Fix MacOSX since "imported" and "Imported::imported" are ambiguous. Test ↵Greg Clayton2015-09-161-2/+9
| | | | | | that we can read the global when specified with the global namespace and test that we can read "Imported::imported" correctly. The commented out test should be testing for ambiguity when just "imported" is evaluated as an expression, but that doesn't work yet. llvm-svn: 247764
* Search variables based on clang::DeclContext and clang::Decl treePaul Herman2015-09-152-3/+80
| | | | | | | | | | | | Summary: SymbolFileDWARF now creates VarDecl and BlockDecl and adds them to the Decl tree. Then, in ClangExpressionDeclMap it uses the Decl tree to search for a variable. This fixes lots of variable scoping problems. Reviewers: sivachandra, chaoren, spyffe, clayborg Subscribers: tberghammer, jingham, lldb-commits Differential Revision: http://reviews.llvm.org/D12658 llvm-svn: 247746
* Clean up register naming conventions inside lldb. Jason Molenda2015-09-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "gcc" register numbers are now correctly referred to as "ehframe" register numbers. In almost all cases, ehframe and dwarf register numbers are identical (the one exception is i386 darwin where ehframe regnums were incorrect). The old "gdb" register numbers, which I incorrectly thought were stabs register numbers, are now referred to as "Process Plugin" register numbers. This is the register numbering scheme that the remote process controller stub (lldb-server, gdbserver, core file support, kdp server, remote jtag devices, etc) uses to refer to the registers. The process plugin register numbers may not be contiguous - there are remote jtag devices that have gaps in their register numbering schemes. I removed all of the enums for "gdb" register numbers that we had in lldb - these were meaningless - and I put LLDB_INVALID_REGNUM in all of the register tables for the Process Plugin regnum slot. This change is almost entirely mechnical; the one actual change in here is to ProcessGDBRemote.cpp's ParseRegisters() which parses the qXfer:features:read:target.xml response. As it parses register definitions from the xml, it will assign sequential numbers as the eRegisterKindLLDB numbers (the lldb register numberings must be sequential, without any gaps) and if the xml file specifies register numbers, those will be used as the eRegisterKindProcessPlugin register numbers (and those may have gaps). A J-Link jtag device's target.xml does contain a gap in register numbers, and it only specifies the register numbers for the registers after that gap. The device supports many different ARM boards and probably selects different part of its register file as appropriate. http://reviews.llvm.org/D12791 <rdar://problem/22623262> llvm-svn: 247741
* Add JUnit/XUnit-formatted output to the lldb test run systemTodd Fiala2015-09-156-114/+1537
| | | | | | | | Also introduces the test event system into our test runner framework. See the following for details: http://reviews.llvm.org/D12831 llvm-svn: 247722
* Skip TestGoASTContext on remote targets as it it not remote compatibleTamas Berghammer2015-09-151-0/+1
| | | | llvm-svn: 247690
* Add support for DW_OP_GNU_const_index to dwarf expressionTamas Berghammer2015-09-151-1/+1
| | | | | | | | DW_OP_GNU_const_index is a new opcode used when split dwarf is enabled Differential revision: http://reviews.llvm.org/D12849 llvm-svn: 247672
* Mark TestMultipleDebuggers as flakey on Darwin.Todd Fiala2015-09-151-0/+1
| | | | | | | See if this gets us past a few machines that are failing it when it is expected to pass. llvm-svn: 247665
* 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
OpenPOWER on IntegriCloud