[lldb-dev] [Bug 25921] New: 3.7 LLDB is broken on i686, while 3.8 (trunk) is just fine
https://llvm.org/bugs/show_bug.cgi?id=25921 Bug ID: 25921 Summary: 3.7 LLDB is broken on i686, while 3.8 (trunk) is just fine Product: lldb Version: 3.7 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: costamagnagianfra...@yahoo.it CC: llvm-b...@lists.llvm.org Classification: Unclassified As said in the title llvm 3.7 doesn't build on ubuntu i386 (that defaults to i686). the problem is an LLDB test failure. https://launchpad.net/ubuntu/+source/llvm-toolchain-3.7/1:3.7.1-1ubuntu1/+build/8427360 I came to two conclusions: disable the testsuite for lldb, or disable all lldb (the latter seems to be the more convenient) https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.7/+bug/1527865 hovewer seems that 3.8 svn doesn't have this issue, so I guess it is just a matter of cherry-picking some bits, assuming somebody knows where they are :) thanks a lot! Gianfranco -- You are receiving this mail because: You are the assignee for the bug. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25922] New: lldbinline.py-style tests will not rerun
https://llvm.org/bugs/show_bug.cgi?id=25922 Bug ID: 25922 Summary: lldbinline.py-style tests will not rerun Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: todd.fi...@gmail.com CC: llvm-b...@lists.llvm.org Classification: Unclassified The test rerun facility cannot run tests implemented through the lldbinline.py convenience wrapper. The issue appears to be that the actual TestCase class comes from lldbtest.py, so the rerun logic (when it asks for the TestCase class path) is attempting to rerun lldbtest.py. This is both incorrect vs. intent and is not useful. I am going to attempt to add an attribute to the test case class created by lldbsuite.test.lldbinline.MakeInlineTest, and have the test infrastructure first check for that and use that attribute if present before falling back to using the path of the class name. This probably would also fix what I imagine is a bug in the output of test issues, as other code in output generation looks at the test case filename. -- You are receiving this mail because: You are the assignee for the bug. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25922] lldbinline.py-style tests will not rerun
https://llvm.org/bugs/show_bug.cgi?id=25922 Todd Fiala changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|lldb-dev@lists.llvm.org |todd.fi...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25924] New: TestEvents sometimes generating SIGSEGV on OS X
https://llvm.org/bugs/show_bug.cgi?id=25924 Bug ID: 25924 Summary: TestEvents sometimes generating SIGSEGV on OS X Product: lldb Version: unspecified Hardware: Macintosh OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: todd.fi...@gmail.com CC: llvm-b...@lists.llvm.org Classification: Unclassified Now that we're piping exceptional exit information properly through the test runner, I'm seeing TestEvents.py occasionally exit with a SIGSEGV: ERROR: [EXCEPTIONAL EXIT 11 (SIGSEGV)] test_listen_for_and_print_event_dsym (python_api/event/TestEvents.py) We need to track this down. I will skip this whole test suite until we can identify the cause of it. Right now it is one of the last things that will intermittently poke through the rerun logic. -- You are receiving this mail because: You are the assignee for the bug. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25925] New: TestCppNsImport failing on FreeBSD with clang
https://llvm.org/bugs/show_bug.cgi?id=25925 Bug ID: 25925 Summary: TestCppNsImport failing on FreeBSD with clang Product: lldb Version: unspecified Hardware: PC OS: FreeBSD Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: ema...@freebsd.org CC: llvm-b...@lists.llvm.org Classification: Unclassified This test is marked xfail for gcc >= 4.9; it also fails on FreeBSD with clang. FAIL: LLDB (/usr/bin/clang-x86_64) :: test_with_run_command_dwarf (TestCppNsImport.TestCppNsImport) == FAIL: test_with_run_command_dwarf (TestCppNsImport.TestCppNsImport) Tests imported namespaces in C++. -- Traceback (most recent call last): File "/tank/emaste/src/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2263, in dwarf_test_method return attrvalue(self) File "/tank/emaste/src/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 608, in wrapper func(*args, **kwargs) File "/tank/emaste/src/llvm/tools/lldb/packages/Python/lldbsuite/test/lang/cpp/nsimport/TestCppNsImport.py", line 55, in test_with_run_command self.assertTrue(test_result.IsValid() and test_result.GetValueAsSigned() == 1, "N::n = 1") AssertionError: False is not True : N::n = 1 Config=x86_64-/usr/bin/clang -- Ran 1 test in 0.950s RESULT: FAILED (0 passes, 1 failures, 0 errors, 0 skipped, 0 expected failures, 0 unexpected successes) [TestCppNsImport.py FAILED] -- You are receiving this mail because: You are the assignee for the bug. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
