<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/packages/Python/lldbsuite/test/lang/cpp/scope, 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-09-04T07:46:25+00:00</updated>
<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>[lldbsuite] Un-xfail tests on Windows that are now passing (pt.5)</title>
<updated>2018-12-20T02:04:01+00:00</updated>
<author>
<name>Stella Stamenova</name>
<email>stilis@microsoft.com</email>
</author>
<published>2018-12-20T02:04:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=6314b92331d0bf5518152540cfbcbd71548f5668'/>
<id>urn:sha1:6314b92331d0bf5518152540cfbcbd71548f5668</id>
<content type='text'>
This is a set of tests that were all marked as failing becuse of pr24764. The bug is not fixed (as in more of the tests that were marked this way are failing), but this set is passing. It is possible that some of them are false positives, but there's a large number of unexpectedly passing tests on Windows, so I am doing a bulk un-xfail to get the buildbot to green.

llvm-svn: 349719
</content>
</entry>
<entry>
<title>Fix whitespace in the python test suite.</title>
<updated>2018-07-27T22:20:59+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2018-07-27T22:20:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=23d7a9ebbe6fd815af1f7263197df701c784d012'/>
<id>urn:sha1:23d7a9ebbe6fd815af1f7263197df701c784d012</id>
<content type='text'>
Summary:
The test suite has often unnecessary trailing whitespace, and sometimes
unnecessary trailing lines or a missing final new line. This patch just strips
trailing whitespace/lines and adds missing newlines at the end.

Subscribers: ki.stfu, JDevlieghere, christof, lldb-commits

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

llvm-svn: 338171
</content>
</entry>
<entry>
<title>Compile the LLDB tests out-of-tree.</title>
<updated>2018-01-30T18:29:16+00:00</updated>
<author>
<name>Adrian Prantl</name>
<email>aprantl@apple.com</email>
</author>
<published>2018-01-30T18:29:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5ec76fe720e43a9196d3437e1ff448668bf7db6d'/>
<id>urn:sha1:5ec76fe720e43a9196d3437e1ff448668bf7db6d</id>
<content type='text'>
This patch is the result of a discussion on lldb-dev, see
http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for
background.

For each test (should be eventually: each test configuration) a
separate build directory is created and we execute

  make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test

In order to make this work all LLDB tests need to be updated to find
the executable in the test build directory, since CWD still points at
the test's source directory, which is a requirement for unittest2.

Although we have done extensive testing, I'm expecting that this first
attempt will break a few bots. Please DO NOT HESITATE TO REVERT this
patch in order to get the bots green again. We will likely have to
iterate on this some more.

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

llvm-svn: 323803
</content>
</entry>
<entry>
<title>Wrap all references to build artifacts in the LLDB testsuite (NFC)</title>
<updated>2018-01-19T23:24:35+00:00</updated>
<author>
<name>Adrian Prantl</name>
<email>aprantl@apple.com</email>
</author>
<published>2018-01-19T23:24:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=595048f3ecf3317aa2d32bed5141a526415f5aea'/>
<id>urn:sha1:595048f3ecf3317aa2d32bed5141a526415f5aea</id>
<content type='text'>
in TestBase::getBuildArtifact(). This NFC commit is in preparation for
https://reviews.llvm.org/D42281 (compile the LLDB tests out-of-tree).

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

llvm-svn: 323007
</content>
</entry>
<entry>
<title>[TestCppScope] This test now passes on Darwin.</title>
<updated>2017-12-12T02:32:49+00:00</updated>
<author>
<name>Davide Italiano</name>
<email>davide@freebsd.org</email>
</author>
<published>2017-12-12T02:32:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4b13d8bdf3c46f6f07a7343d0365a9a88554e6bb'/>
<id>urn:sha1:4b13d8bdf3c46f6f07a7343d0365a9a88554e6bb</id>
<content type='text'>
I tested on x86-64 and Jason on embedded architectures.
This cleans up another couple of reported unexpected successes.

&lt;rdar://problem/28623427&gt;

llvm-svn: 320452
</content>
</entry>
<entry>
<title>Fixup the xfail situation on Windows.</title>
<updated>2016-10-05T20:47:17+00:00</updated>
<author>
<name>Zachary Turner</name>
<email>zturner@google.com</email>
</author>
<published>2016-10-05T20:47:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=9c69bc9776110df35cb538d6709bf2f20a98b35c'/>
<id>urn:sha1:9c69bc9776110df35cb538d6709bf2f20a98b35c</id>
<content type='text'>
Xfails added and/or removed to reflect the current state of Windows.

llvm-svn: 283380
</content>
</entry>
<entry>
<title>The collision of class C and libsystem_c.dylib:C is a failure</title>
<updated>2016-10-05T01:19:15+00:00</updated>
<author>
<name>Jim Ingham</name>
<email>jingham@apple.com</email>
</author>
<published>2016-10-05T01:19:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=9ff9713f8a2fba396e4d40cb180b52a896e5bdd1'/>
<id>urn:sha1:9ff9713f8a2fba396e4d40cb180b52a896e5bdd1</id>
<content type='text'>
worth preserving, but not essential to the purpose of this test
so I broke it into a separate test.

llvm-svn: 283289
</content>
</entry>
<entry>
<title>This test is failing because there's a global symbol "C" in libsystem_c.dylib,</title>
<updated>2016-10-05T01:09:43+00:00</updated>
<author>
<name>Jim Ingham</name>
<email>jingham@apple.com</email>
</author>
<published>2016-10-05T01:09:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=f5fe75a6e0c66d5bb81a6ffd8906d66cb7f34f2f'/>
<id>urn:sha1:f5fe75a6e0c66d5bb81a6ffd8906d66cb7f34f2f</id>
<content type='text'>
and that is defeating the lookup of the "struct C" here.  Adding the bug for that.

llvm-svn: 283287
</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>
</feed>
