bcm5719-llvm/lldb/packages/Python/lldbsuite/test/api, branch meklort-10.0.1Project Ortega BCM5719 LLVMhttps://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.12019-12-26T15:49:35+00:00[lldb][NFC] Simplify if-return2019-12-26T15:49:35+00:00Tatyana Krasnukhatatyana@synopsys.com2019-12-11T14:16:38+00:00urn:sha1:04359f48f02105d15ad1dd7e8d83801260794e18[lldb][NFC] Remove all `setUp` overrides that only call the parent implementation2019-12-13T11:34:49+00:00Raphael Isemannteemperor@gmail.com2019-12-13T11:24:23+00:00urn:sha1:9bace26a690a778ec0f09a9aae9537dfbdb6f42f
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
[lldb][NFC] Remove 'from __future__ import print_function' from all tests that don't actually call 'print()'2019-12-13T11:23:04+00:00Raphael Isemannteemperor@gmail.com2019-12-13T11:11:23+00:00urn:sha1:a52a11139c0e3db9b00079aa1516080742b79475
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
[lldb] [testsuite] Mark TestSBCommandReturnObject as failing on Windows2019-10-04T20:49:44+00:00Jan Kratochviljan.kratochvil@redhat.com2019-10-04T20:49:44+00:00urn:sha1:4c7b8421856ee677b6a7ad4af844dcde647de960
Filed:
testsuite: TestSBCommandReturnObject: object has no attribute 'dylibPath'
https://bugs.llvm.org/show_bug.cgi?id=43570
http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja/builds/9530/steps/test/logs/stdio
AttributeError: 'TestSBCommandReturnObject' object has no attribute 'dylibPath'
Fix crash on SBCommandReturnObject & assignment
https://reviews.llvm.org/D67589
env = {self.dylibPath: self.getLLDBLibraryEnvVal()}
I do not know how to link with liblldb on Windows so marking it as failing on
Windows.
llvm-svn: 373787
[lldb] Fix crash on SBCommandReturnObject & assignment2019-10-04T19:32:57+00:00Jan Kratochviljan.kratochvil@redhat.com2019-10-04T19:32:57+00:00urn:sha1:4112b4733502f746b766861853c414af0e01d6f9
I was writing an SB API client and it was crashing on:
bool DoExecute(SBDebugger dbg, char **command, SBCommandReturnObject &result) {
result = subcommand(dbg, "help");
That is because SBCommandReturnObject &result gets initialized inside LLDB by:
bool DoExecute(Args &command, CommandReturnObject &result) override {
// std::unique_ptr gets initialized here from `&result`!!!
SBCommandReturnObject sb_return(&result);
DoExecute(...);
sb_return.Release();
Differential revision: https://reviews.llvm.org/D67589
llvm-svn: 373775
Revert: [lldb] [testsuite] Remove redundant MAKE_DSYM := NO2019-09-27T18:52:34+00:00Jan Kratochviljan.kratochvil@redhat.com2019-09-27T18:52:34+00:00urn:sha1:dce7edf7e67ad0622b02b5c9cbffafe42b5df131
Revert: llvm-svn: 373061
It broke OSX testsuite:
https://reviews.llvm.org/D67589#1686150
lldb/packages/Python/lldbsuite/test/macosx/function-starts/TestFunctionStarts.py
llvm-svn: 373110
[lldb] [testsuite] Remove redundant MAKE_DSYM := NO2019-09-27T09:59:53+00:00Jan Kratochviljan.kratochvil@redhat.com2019-09-27T09:59:53+00:00urn:sha1:32a4b27aa3c906e62c532d2372fa5e7db1c0c452
According to a comment by Pavel Labath:
https://reviews.llvm.org/D67589#inline-612375
llvm-svn: 373061
Fir TestAPILog for gcc2019-09-18T13:41:50+00:00Pavel Labathpavel@labath.sk2019-09-18T13:41:50+00:00urn:sha1:89ad7f7a1ba245fccf1f64f95a146ada6f6aaac6
different compilers will put different things into __PRETTY_FUNCTION__.
For instance gcc will not put a " " in the "const char *" argument,
causing our regex matching to fail.
This patch relaxes the regexes in this test to account for this
difference.
llvm-svn: 372224
[test] Fail gracefully if the regex doesn't match2019-09-16T23:49:42+00:00Jonas Devliegherejonas@devlieghere.com2019-09-16T23:49:42+00:00urn:sha1:71b32e4175d111e1d2a62bf681b5c49e92ff163a
This test is failing on the Fedora bot (staging). Rather than failing
with an IndexError, we should trigger an assert and dump the log when
the regex doesn't match.
llvm-svn: 372052
[test] Update TestAPILog to pass on Windows.2019-09-13T22:14:59+00:00Jonas Devliegherejonas@devlieghere.com2019-09-13T22:14:59+00:00urn:sha1:61dc038f8de01ce765387fa06d8cd5d9276cf62f
The pretty function macro is including __cdecl on Windows, which was
causing the pattern matching to fail. This should fix that.
llvm-svn: 371905