<rdar://problem/12362092>

The decorators @expectedFailure (plain and special-case like i386, clang, ...) are modified to optionally take a bugnumber argument
If such an argument is specified, the failure report (or unexpected success report) will include the information passed in as part of the message
This is mostly useful for associating failures to issue IDs in issue management systems (e.g. the LLVM bugzilla)



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175942 91177308-0d34-0410-b5e6-96231b3b80d8
Remove no-op code (since r175842)


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175944 91177308-0d34-0410-b5e6-96231b3b80d8
Fixing issues in previous checkin - still figuring out how to make expectedFailureClang take the bugnumber

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175945 91177308-0d34-0410-b5e6-96231b3b80d8
This should get clang/gcc decorators working

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175946 91177308-0d34-0410-b5e6-96231b3b80d8