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

[Pavel Labath via lldb-commits]

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....