<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/packages/Python/lldbsuite/test/commands/command/script, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2020-01-10T13:39:38+00:00</updated>
<entry>
<title>[lldb][tests] Cleanup '.categories'</title>
<updated>2020-01-10T13:39:38+00:00</updated>
<author>
<name>Tatyana Krasnukha</name>
<email>tatyana@synopsys.com</email>
</author>
<published>2019-12-11T16:33:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b3af8ab7f83c2a825c584ddedf5cc9207ca66b44'/>
<id>urn:sha1:b3af8ab7f83c2a825c584ddedf5cc9207ca66b44</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[lldb][NFC] Remove all `setUp` overrides that only call the parent implementation</title>
<updated>2019-12-13T11:34:49+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-12-13T11:24:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=9bace26a690a778ec0f09a9aae9537dfbdb6f42f'/>
<id>urn:sha1:9bace26a690a778ec0f09a9aae9537dfbdb6f42f</id>
<content type='text'>
Summary:
A lot of our tests copied the setUp code from our TestSampleTest.py:

```
    def setUp(self):
        # Call super's setUp().
        TestBase.setUp(self)
```

This code does nothing unless we actually do any setUp work in there, so let's remove all these method definitions.

Reviewers: labath, JDevlieghere

Reviewed By: labath

Subscribers: lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D71454
</content>
</entry>
<entry>
<title>[lldb][NFC] Remove 'from __future__ import print_function' from all tests that don't actually call 'print()'</title>
<updated>2019-12-13T11:23:04+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-12-13T11:11:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a52a11139c0e3db9b00079aa1516080742b79475'/>
<id>urn:sha1:a52a11139c0e3db9b00079aa1516080742b79475</id>
<content type='text'>
Summary:
A lot of tests do this trick but the vast majority of them don't even call `print()`.

Most of this patch was generated by a script that just looks at all the files and deletes the line if there is no `print (` or `print(` anywhere else in the file.
I checked the remaining tests manually and deleted the import if we never call print (but instead do stuff like `expr print(...)` and similar false-positives).
I also corrected the additional empty lines after the import in the files that I manually edited.

Reviewers: JDevlieghere, labath, jfb

Reviewed By: labath

Subscribers: dexonsmith, wuzish, nemanjai, kbarton, christof, arphaman, abidh, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D71452
</content>
</entry>
<entry>
<title>[LLDB] bugfix: command script add -f doesn't work for some callables</title>
<updated>2019-10-19T07:05:33+00:00</updated>
<author>
<name>Lawrence D'Anna</name>
<email>lawrence_danna@apple.com</email>
</author>
<published>2019-10-19T07:05:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2386537c2469a97501a305c6b3138231b907a67f'/>
<id>urn:sha1:2386537c2469a97501a305c6b3138231b907a67f</id>
<content type='text'>
Summary:
When users define a debugger command from python, they provide a callable
object.   Because the signature of the function has been extended, LLDB
needs to inspect the number of parameters the callable can take.

The rule it was using to decide was weird, apparently not tested, and
giving wrong results for some kinds of python callables.

This patch replaces the weird rule with a simple one: if the callable can
take 5 arguments, it gets the 5 argument version of the signature.
Otherwise it gets the old 4 argument version.

It also adds tests with a bunch of different kinds of python callables
with both 4 and 5 arguments.

Reviewers: JDevlieghere, clayborg, labath, jingham

Reviewed By: labath

Subscribers: lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D69014

llvm-svn: 375333
</content>
</entry>
<entry>
<title>[dotest] Avoid the need for LEVEL= makefile boilerplate</title>
<updated>2019-09-04T07:46:25+00:00</updated>
<author>
<name>Pavel Labath</name>
<email>pavel@labath.sk</email>
</author>
<published>2019-09-04T07:46:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=418a272f4ab4221c37a9272d48fd31d5ac1bddc1'/>
<id>urn:sha1:418a272f4ab4221c37a9272d48fd31d5ac1bddc1</id>
<content type='text'>
Summary:
Instead of each test case knowing its depth relative to the test root,
we can just have dotest add the folder containing Makefile.rules to the
include path.

This was motivated by r370616, though I have been wanting to do this
ever since we moved to building tests out-of-tree.

The only manually modified files in this patch are lldbinline.py and
plugins/builder_base.py. The rest of the patch has been produced by this
shell command:
  find . \( -name Makefile -o -name '*.mk' \)  -exec sed --in-place -e '/LEVEL *:\?=/d' -e '1,2{/^$/d}' -e 's,\$(LEVEL)/,,' {} +

Reviewers: teemperor, aprantl, espindola, jfb

Subscribers: emaste, javed.absar, arichardson, christof, arphaman, lldb-commits

Differential Revision: https://reviews.llvm.org/D67083

llvm-svn: 370845
</content>
</entry>
<entry>
<title>[lldb][NFC] Fix failing tests after restructuring test folder</title>
<updated>2019-09-01T13:36:44+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-09-01T13:36:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3e15a7a147e95fa99aab95aa9541ab46ba96b2a2'/>
<id>urn:sha1:3e15a7a147e95fa99aab95aa9541ab46ba96b2a2</id>
<content type='text'>
Just adjusts all the relative paths in the Makefiles (and
the breakpoint test which seems to rely on the name of its
folder).

llvm-svn: 370611
</content>
</entry>
<entry>
<title>[lldb] Restructure test folders to match LLDB command hierarchy</title>
<updated>2019-09-01T09:12:37+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-09-01T09:12:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=29872606d220420d53fde7cc5e3bea15f8da62e7'/>
<id>urn:sha1:29872606d220420d53fde7cc5e3bea15f8da62e7</id>
<content type='text'>
Summary:
As discussed on lldb-dev, this patch moves some LLDB tests into a hierarchy that more closely
resembles the commands we use in the LLDB interpreter. This patch should only move tests
that use the command interpreter and shouldn't touch any tests that primarily test the SB API.

Reviewers: #lldb, jfb, JDevlieghere

Reviewed By: #lldb, JDevlieghere

Subscribers: dexonsmith, arphaman, JDevlieghere, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D67033

llvm-svn: 370605
</content>
</entry>
</feed>
