These are real failures. They are due to a Swift change that is emitting invalid symbols. Lang/Roman are working on a fix. I didn’t mark these as failures because they are working on the fix.
If we wanted to limit noise, the right thing to do here would have been to revert that change until they could work out the bad symbol names reported by the JIT. (I was okay with not insisting on that because they were going to quickly track this down).
On Mar 3, 2016, at 1:31 PM, Ben Langmuir via swift-lldb-dev <firstname.lastname@example.org> wrote:
This is the same old failure we’ve been seeing for a while. I filed a radar to improve the “new issue” detection so it won’t send all these false positives for lldb tests:
<rdar://problem/24961012 <rdar://problem/24961012>> Don't report "new issue" when test failures happen in different orders
On Mar 3, 2016, at 1:20 PM, email@example.com <mailto:firstname.lastname@example.org> wrote:
swift-lldb-dev mailing list