I'm ignoring this again because I only made Swift-side changes that shouldn't affect LLDB, but that's rather dangerous. Todd, was this the issue you were looking at?
Jordan
···
On Apr 14, 2016, at 16:39, no-reply@swift.org wrote:
I'm OOO until Monday. I fixed a race that was exacerbated by the merge, but there is another issue behind that. The way to be safe, if you care, is look at the rerun tests. Only the things that fail on rerun, which was none in this case, are real issues.
This is unfortunate and I will address when I get back. I spent yesterday addressing a race that blocked further diagnosis of this issue manifesting here.
-Todd
···
On Apr 14, 2016, at 4:43 PM, Jordan Rose via swift-lldb-dev <swift-lldb-dev@swift.org> wrote:
I'm ignoring this again because I only made Swift-side changes that shouldn't affect LLDB, but that's rather dangerous. Todd, was this the issue you were looking at?
Jordan
On Apr 14, 2016, at 16:39, no-reply@swift.org wrote: