summaryrefslogtreecommitdiffstats
path: root/debuginfo-tests/dexter/dex
Commit message (Collapse)AuthorAgeFilesLines
* [dexter] Fix feature tests on WindowsReid Kleckner2019-11-052-2/+4
| | | | | | | | | | | | | | | | | | | | | First, add LLD as a dependency on Windows. The windows batch scripts pass -fuse-ld=lld, so they need it. Second, decode builder stdout/stderr even if the command fails. Otherwise it gets printed as b'line 1\n\rline 2\n\r'. Last, make the batch script one line less noisy. We might want to try to do more here, though. It would be nice if we could get as close to possible as lit, where you can literally copy & paste the failing command to re-run it. With the two changes above, now the feature tests that use clang++.bat pass for me. The clang-cl_vs2015 ones still fail, and I'll fix them separately. Reviewers: jmorse Differential Revision: https://reviews.llvm.org/D69725
* [Dexter] Continue sprinking no-location fixesJeremy Morse2019-11-011-1/+1
| | | | | | | | | Example failure: http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/3255/testReport/junit/debuginfo-tests/dexter-tests/asan_c/ The tests themselves seem to be working, it's just unexplored paths within dexter that are flaking out.
* [Dexter] Account for another no-lineno scenarioJeremy Morse2019-11-011-1/+2
| | | | | This is another part of Dexter that had never seen a missing source location before, now newly turning up on Darwin.
* [Dexter] Cope better with empty source locationsJeremy Morse2019-11-011-0/+2
| | | | | | When running a program, Dexter single steps if it's in one of the source files under test, or free-runs if it isn't. Handle the circumstance where the current source file simply isn't known.
* Fix a brain-fail with debuginfo-tests/dexter internal testsJeremy Morse2019-11-011-0/+2
| | | | | | | | | | | | I baked the "test" subcommand into the %dexter substituion, as that's what all of the dexter tests use. However I forgot about the internal tests for whether dexters features are working. Install a %dexter_base command to allow those tests to call dexter.py directly, and un-xfail the tests on darwin. Update too the list of paths the unittests shouldn't try and cover, as it tries to load dbgeng on unix machines. Ideally we wouldn't be using this method of test discovery in the future.
* Reapply "Import Dexter to debuginfo-tests""Jeremy Morse2019-10-3189-0/+7918
| | | | | | | This reverts commit cb935f345683194e42e6e883d79c5a16479acd74. Discussion in D68708 advises that green dragon is being briskly refurbished, and it's good to have this patch up testing it.
* Revert "Import Dexter to debuginfo-tests"Jeremy Morse2019-10-3189-7918/+0
| | | | | | This reverts commit f78c236efda85af1e526ac35ed535ef4786450e3. Green dragon breakage was observed; I'll take a look at why.
* Import Dexter to debuginfo-testsJeremy Morse2019-10-3189-0/+7918
Dexter (Debug Experience Tester) is a test-driver for our debug info integration tests, reading a set of debug experience expectations and comparing them with the actual behaviour of a program under a debugger. More about Dexter can be found in the RFC: http://lists.llvm.org/pipermail/llvm-dev/2019-October/135773.html and the phab review in D68708. Not all the debuginfo tests have been transformed into Dexter tests, and we look forwards to doing that incrementally. This commit mostly aims to flush out buildbots that are running debuginfo-tests but don't have python 3 installed, possibly green-dragon and some windows bots.
OpenPOWER on IntegriCloud