[Lldb-commits] [PATCH] D16825: [Windows] Set correct thread stop info when single-step lands on a breakpoint

Adrian McCarthy via lldb-commits lldb-commits at lists.llvm.org
Wed Feb 3 08:19:19 PST 2016

Ah, I missed the "not_in" in that decorator.  Thanks.

On Wed, Feb 3, 2016 at 1:38 AM, Pavel Labath <labath at google.com> wrote:

> On 2 February 2016 at 23:08, Adrian McCarthy via lldb-commits
> <lldb-commits at lists.llvm.org> wrote:
> > Thanks for the confirmation.  I'm still not sure how
> TestConsecutiveBreakpoints.py used to work on Windows, but I believe this
> is the right fix.
> The test used to be marked with
> "@expectedFailureAll("llvm.org/pr23478", oslist =
> not_in(["macosx"]))", so I guess you were just not seeing the failure.
> When Abhishek landed the first fix (r259344), he removed the
> decorator, so the test was now suddenly being run....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20160203/b1ea8dec/attachment-0001.html>

More information about the lldb-commits mailing list