[lldb-dev] [Lldb-commits] [lldb] r183281 - Re-enabling a test that is no longer failing
ashok.thirumurthi at intel.com
Fri Jun 7 13:54:48 PDT 2013
I believe this test is causing the clang buildbot to hang. The trick to reproduce the failure is to run "make check" from build/tools/lldb/test. Note that this uses dosep.py to run the tests. In comparison, tools/lldb/test/dotest.py runs to completion. I'm not sure why Tuesday's commit started to hang consistently from Thursday night, but it could have something to do with the order in which tests are run now.
As "make check" runs to completion when I revert this commit, I'll commit that change to see how it pans out on the buildbots...
From: lldb-commits-bounces at cs.uiuc.edu [mailto:lldb-commits-bounces at cs.uiuc.edu] On Behalf Of Andrew Kaylor
Sent: Tuesday, June 04, 2013 7:39 PM
To: lldb-commits at cs.uiuc.edu
Subject: [Lldb-commits] [lldb] r183281 - Re-enabling a test that is no longer failing
Date: Tue Jun 4 18:38:51 2013
New Revision: 183281
Re-enabling a test that is no longer failing
--- lldb/trunk/test/functionalities/thread/break_after_join/TestBreakAfterJoin.py (original)
+++ lldb/trunk/test/functionalities/thread/break_after_join/TestBreakAfterJoin.py Tue Jun 4 18:38:51 2013
@@ -21,7 +21,6 @@ class BreakpointAfterJoinTestCase(TestBa
@expectedFailureDarwin("llvm.org/pr15824") # thread states not properly maintained
- @skipIfLinux # Fails intermittently, llvm.org/pr16170"
"""Test breakpoint handling after a thread join."""
lldb-commits mailing list
lldb-commits at cs.uiuc.edu
More information about the lldb-dev