<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/packages/Python/lldbsuite/test/test_runner, 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>2019-12-13T11:23:04+00:00</updated>
<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][NFC] Remove unused imports in python tests</title>
<updated>2019-08-02T08:06:22+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-08-02T08:06:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=9eedbc4f266d1e49d335d48c4c0f717401d927d2'/>
<id>urn:sha1:9eedbc4f266d1e49d335d48c4c0f717401d927d2</id>
<content type='text'>
llvm-svn: 367663
</content>
</entry>
<entry>
<title>Bring Doxygen comment syntax in sync with LLVM coding style.</title>
<updated>2019-03-11T17:09:29+00:00</updated>
<author>
<name>Adrian Prantl</name>
<email>aprantl@apple.com</email>
</author>
<published>2019-03-11T17:09:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=f05b42e960a9badf37e17d896d5764ef9ffce8f2'/>
<id>urn:sha1:f05b42e960a9badf37e17d896d5764ef9ffce8f2</id>
<content type='text'>
This changes '@' prefix to '\'.

llvm-svn: 355841
</content>
</entry>
<entry>
<title>Update the file headers across all of the LLVM projects in the monorepo</title>
<updated>2019-01-19T08:50:56+00:00</updated>
<author>
<name>Chandler Carruth</name>
<email>chandlerc@gmail.com</email>
</author>
<published>2019-01-19T08:50:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2946cd701067404b99c39fb29dc9c74bd7193eb3'/>
<id>urn:sha1:2946cd701067404b99c39fb29dc9c74bd7193eb3</id>
<content type='text'>
to reflect the new license.

We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.

Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.

llvm-svn: 351636
</content>
</entry>
<entry>
<title>NFC: Fix some comment typos.</title>
<updated>2018-05-28T04:22:07+00:00</updated>
<author>
<name>Bob Wilson</name>
<email>bob.wilson@apple.com</email>
</author>
<published>2018-05-28T04:22:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=c791417a6d17851dcb0a0ee217d2c7ac463e3c47'/>
<id>urn:sha1:c791417a6d17851dcb0a0ee217d2c7ac463e3c47</id>
<content type='text'>
llvm-svn: 333364
</content>
</entry>
<entry>
<title>added Linux support for test timeout sampling</title>
<updated>2016-09-26T20:25:47+00:00</updated>
<author>
<name>Todd Fiala</name>
<email>todd.fiala@gmail.com</email>
</author>
<published>2016-09-26T20:25:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2cd84c905df4fe9a6005320a45e98cd4b8ade045'/>
<id>urn:sha1:2cd84c905df4fe9a6005320a45e98cd4b8ade045</id>
<content type='text'>
This is the Linux counterpart to the sampling support I added
on the macOS side.

This change also introduces zip-file compression if the size of
the sample output is greater than 10 KB.  The Linux side can be
quite large and the textual content is averaging over a 10x
compression factor on tests that I force to time out.  When
compression takes place, the filename becomes:

    {session_dir}/{TestFilename.py}-{pid}.sample.zip

This support relies on the linux 'perf' tool.  If it isn't
present, the behavior is to ignore pre-kill processing of
the timed out test process.

Note calling the perf tool under the timeout command appears
to nuke the profiled process.  This was causing the timeout
kill logic to fail due to the process having disappeared.
I modified the kill logic to catch the case of the process
not existing, and I have it ignore the kill request in that
case.  Any other exception is still raised.

Reviewers: labath

Subscribers: lldb-commits

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

llvm-svn: 282436
</content>
</entry>
<entry>
<title>add hook for calling platform-dependent pre-kill action on a timed out test</title>
<updated>2016-09-23T16:10:01+00:00</updated>
<author>
<name>Todd Fiala</name>
<email>todd.fiala@gmail.com</email>
</author>
<published>2016-09-23T16:10:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=72525622b2f2f558dfd2a5a37577b0f6e3ae16a1'/>
<id>urn:sha1:72525622b2f2f558dfd2a5a37577b0f6e3ae16a1</id>
<content type='text'>
differential review: https://reviews.llvm.org/D24850

reviewers: clayborg, labath
llvm-svn: 282258
</content>
</entry>
<entry>
<title>*** This commit represents a complete reformatting of the LLDB source code</title>
<updated>2016-09-06T20:57:50+00:00</updated>
<author>
<name>Kate Stone</name>
<email>katherine.stone@apple.com</email>
</author>
<published>2016-09-06T20:57:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b9c1b51e45b845debb76d8658edabca70ca56079'/>
<id>urn:sha1:b9c1b51e45b845debb76d8658edabca70ca56079</id>
<content type='text'>
*** to conform to clang-format’s LLVM style.  This kind of mass change has
*** two obvious implications:

Firstly, merging this particular commit into a downstream fork may be a huge
effort.  Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit.  The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):

    find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
    find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;

The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.

Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit.  There are alternatives available that will attempt
to look through this change and find the appropriate prior commit.  YMMV.

llvm-svn: 280751
</content>
</entry>
<entry>
<title>Revert "[test] Report error when inferior test processes exit with a non-zero code"</title>
<updated>2016-07-18T14:42:01+00:00</updated>
<author>
<name>Pavel Labath</name>
<email>labath@google.com</email>
</author>
<published>2016-07-18T14:42:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5ab9732aef3c2d7af071de8492fd7c08e7984025'/>
<id>urn:sha1:5ab9732aef3c2d7af071de8492fd7c08e7984025</id>
<content type='text'>
This reverts r275782.

The problem with the commit is that it reports an additional "exit (1)" error for every file
containing a failing test, which is far more than I had intended to do. I'll need to come up with
a more fine-grained way of achieving the result.

llvm-svn: 275791
</content>
</entry>
<entry>
<title>[test] Report error when inferior test processes exit with a non-zero code</title>
<updated>2016-07-18T11:27:19+00:00</updated>
<author>
<name>Pavel Labath</name>
<email>labath@google.com</email>
</author>
<published>2016-07-18T11:27:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=52bd8012bd0f440e21ddec0c1d6ed89605adbb3b'/>
<id>urn:sha1:52bd8012bd0f440e21ddec0c1d6ed89605adbb3b</id>
<content type='text'>
Summary:
We've run into this problem when the test errored out so early (because it could not connect to
the remote device), that the code in D20193 did not catch the error. This resulted in the test
suite reporting success with 0 tests being run.

This patch makes sure that any non-zero exit code from the inferior process gets reported as an
error. Basically I expand the concept of "exceptional exits", which was previously being used for
signals to cover these cases as well.

Reviewers: tfiala, zturner

Subscribers: lldb-commits

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

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