| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
It's passing all the time for me (50/50), and was passing what
looks like 9/10 times for the originator.
llvm-svn: 247639
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Add GoASTContext and DWARFASTParserGo to support go.
Differential Revision: http://reviews.llvm.org/D12585
llvm-svn: 247629
|
|
|
|
|
|
|
| |
Top of tree is running with no unexpected successes with this
change, on latest available El Capitan and Xcode betas.
llvm-svn: 247608
|
|
|
|
|
|
| |
llvm.org/pr20273
llvm-svn: 247605
|
|
|
|
| |
llvm-svn: 247602
|
|
|
|
|
|
|
|
|
|
| |
TestPersistObjCPointeeType and TestObjCNewSyntax marked up to expect
success on clang >= 7.0.0.
TestMultipleDebuggers passed 25/25 times, taking off intermittent.
If this changes, I'll make sure it goes into a flaky/flakey category.
llvm-svn: 247601
|
|
|
|
|
|
|
|
| |
ExprCommandCallUserDefinedFunction::test_with_dwarf
llvm.org/pr20274
llvm-svn: 247596
|
|
|
|
|
|
|
| |
In ConstVariableTestCase::test_with_dwarf_and_run_command - the test
fails with Clang (and presumably ICC) also on FreeBSD.
llvm-svn: 247594
|
|
|
|
|
|
| |
unexpected successes.
llvm-svn: 247591
|
|
|
|
|
|
|
|
|
| |
TestCallStdStringFunction
TestCallWithTimeout
TestConstVariables
TestClassTypes
llvm-svn: 247576
|
|
|
|
|
|
| |
the test does not know how to run executables on the remote platform.
llvm-svn: 247574
|
|
|
|
|
|
|
|
| |
Related to these two test case classes:
test/driver/batch_mode/TestBatchMode.py
test/functionalities/inferior-assert/TestInferiorAssert.py
llvm-svn: 247567
|
|
|
|
|
|
| |
One or more of these tests failed in 25 of 100 dotest.py runs.
llvm-svn: 247566
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
StopHookForMultipleThreadsTestCase::test_stop_hook_multiple_threads_with_dwarf on FreeBSD
This test passes locally but was disabled due to pexpect issues 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. Noted by John Wolfe.
llvm.org/pr22784
This re-applies r247013.
llvm-svn: 247565
|
|
|
|
|
|
| |
llvm.org/pr18533
llvm-svn: 247564
|
|
|
|
|
|
| |
llvm.org/pr24282
llvm-svn: 247563
|
|
|
|
|
|
|
|
|
|
|
| |
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/pr23747
llvm-svn: 247562
|
|
|
|
| |
llvm-svn: 247552
|
|
|
|
| |
llvm-svn: 247479
|
|
|
|
| |
llvm-svn: 247469
|
|
|
|
|
|
| |
llvm.org/pr24778
llvm-svn: 247460
|
|
|
|
|
|
| |
llvm.org/pr24777
llvm-svn: 247459
|
|
|
|
|
|
| |
llvm.org/pr24772
llvm-svn: 247458
|
|
|
|
|
|
|
|
| |
This is a trivial issue to fix, just marking it for later.
Windows prints function signatures a bit differently, and the
test expects a specific format.
llvm-svn: 247457
|
|
|
|
|
|
| |
llvm.org/pr21765
llvm-svn: 247456
|
|
|
|
|
|
| |
http://llvm.org/pr24764
llvm-svn: 247455
|
|
|
|
|
|
|
|
| |
It turns out it fails consistently for me.
llvm.org/pr19310
llvm-svn: 247411
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes the following case:
```
$ ./dotest.py --executable=~/p/llvm/build_ninja/bin/lldb tools/lldb-mi/
'~/p/llvm/build_ninja/bin/lldb' is not a path to a valid executable
Traceback (most recent call last):
File "./dotest.py", line 1306, in <module>
setupSysPath()
File "./dotest.py", line 1004, in setupSysPath
if not lldbtest_config.lldbExec:
AttributeError: 'module' object has no attribute 'lldbExec'
```
And with this fix:
```
$ ./dotest.py --executable=~/p/llvm/build_ninja/bin/lldb tools/lldb-mi/
'~/p/llvm/build_ninja/bin/lldb' is not a path to a valid executable
The 'lldb' executable cannot be located. Some of the tests may not be run as a result.
```
llvm-svn: 247256
|
|
|
|
|
|
|
|
|
|
| |
It often hangs or times out, and obscures issues with other tests.
Just skip it for now (until the FreeBSD test suite is producing
consistent results) so that we can get a buildbot back.
Previous investigation (for failures) in llvm.org/pr18522
llvm-svn: 247190
|
|
|
|
|
|
|
|
|
| |
We had 2 tests named TestCPPBreakpoints.py. If one of those tests
failed, both of them would be reported as failures and contribute
to the failure count. There may be other examples of duplicate
test names, and we should fix those as we find them.
llvm-svn: 247173
|
|
|
|
|
|
|
|
|
|
|
| |
Due to LLDB or test race conditions these tests do not pass
consistently.
llvm.org/pr15037
llvm.org/pr19310
llvm.org/pr22611
llvm-svn: 247143
|
|
|
|
|
|
|
|
|
| |
The test is hitting an assertion in Clang. This is an extension of
r246766.
llvm.org/pr24691
llvm-svn: 247141
|
|
|
|
|
|
| |
The dwo files are generated when the tests run with split dwarf info.
llvm-svn: 247130
|
|
|
|
|
|
|
|
|
|
| |
See https://llvm.org/bugs/show_bug.cgi?id=24708 for details.
Using '-f FILTER' or unnamed arguments (directories) to dotest.py
will now force no-multiprocessing mode. This stops a bombardment
of test output spam when following the instructions we provide
in a test session trace for rerunning the test.
llvm-svn: 247101
|
|
|
|
|
|
| |
TestRegisters.test_fp_special_purpose_register_read to fail on OSX.
llvm-svn: 247090
|
|
|
|
|
|
|
|
| |
See http://reviews.llvm.org/D12651 for more details.
For the parallel test runner, -v now also implies --output-on-success.
llvm-svn: 247084
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
StopHookForMultipleThreadsTestCase::test_stop_hook_multiple_threads_with_dwarf on FreeBSD"
And update the comment describing the reason this test is skipped.
Unlike the issue described llvm.org/pr22784 this test sometimes causes
a hang on my local machine and is not just a problem on the retired
buildbot.
This reverts commit r247013.
llvm-svn: 247024
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
StopHookForMultipleThreadsTestCase::test_stop_hook_multiple_threads_with_dwarf on FreeBSD
This test passes locally but was disabled due to pexpect issues 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. Noted by John Wolfe.
llvm.org/pr22784
llvm-svn: 247013
|
|
|
|
|
|
|
|
|
|
|
| |
PluginCommandTestCase::test_load_plugin
This test was failing due to a libc++ vs libsdc++ conflict which should
be fixed by r200646.
llvm.org/pr17430
llvm-svn: 247012
|
|
|
|
|
|
| |
Apply test update from r234992 to FreeBSD
llvm-svn: 247009
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
- Bug 24457 can now be tested for inferiors compiled
by clang compiler also.
- A generic test case for GCC and Clang inferiors:
-- Works even when Clang and GCC produce different
assembly for the same inferior.
- Refer Differential Revision: http://reviews.llvm.org/D12677
Signed-off-by: Abhishek Aggarwal <abhishek.a.aggarwal@intel.com>
llvm-svn: 247000
|
|
|
|
| |
llvm-svn: 246972
|
|
|
|
| |
llvm-svn: 246971
|
|
|
|
| |
llvm-svn: 246970
|
|
|
|
| |
llvm-svn: 246966
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
For an array declared like "blk[2][3]", this command was showing:
-data-evaluate-expression blk
^done,value="{[0] = [3], [1] = [3]}"
After this fix, it shows:
-data-evaluate-expression blk
^done,value="{[0] = {[0] = 1, [1] = 2, [2] = 3}, [1] = {[0] = 4, [1] = 5, [2] = 6}}"
The code to do the right thing was already available and used by other commands.
So I have just used that and removed the half-baked previous implementation.
Reviewers: ki.stfu
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D12634
llvm-svn: 246965
|
|
|
|
|
|
| |
it appears a kernel bug is preventing us from writing into the register.
llvm-svn: 246964
|
|
|
|
|
|
|
|
| |
- clang is picky about inline assembly: add the correct instruction size suffix
- mark the new test as expectedFailureClang: the test fails as the breakpoint is set in the wrong
place
llvm-svn: 246957
|
|
|
|
|
|
| |
the test is occasionally failing on linux for all tested scenarios.
llvm-svn: 246956
|