Bob Wilson 00e6bb8690 Reenable Runtime/linux-fatal-backtrace.swift test ...

The best guess so far is that the failure that caused the test to be
disabled was a consequence of not running a clean build to regenerate
the lit.site.cfg file so that the "REQUIRES: lldb" check gave the wrong
answer. rdar://problem/33718631

2017-11-14 11:33:22 -08:00

..

backtrace.swift

tests: replace '// RUN: rm -rf' '// RUN: mkdir' pairs with '%empty-directory(...)'

2017-06-04 11:08:39 -07:00

crash_without_backtrace_optimized.swift

On Linux, make swift_reportError always print backtraces (#10638)

2017-06-27 21:53:55 -07:00

crash_without_backtrace.swift

On Linux, make swift_reportError always print backtraces (#10638)

2017-06-27 21:53:55 -07:00

linux-fatal-backtrace.swift

Reenable Runtime/linux-fatal-backtrace.swift test

2017-11-14 11:33:22 -08:00

weak-reference-racetests-dispatch.swift

IRGen: Fix Dispatch overlay for non-optimized builds

2016-08-13 01:51:45 -07:00

weak-reference-racetests.swift

Use UNSUPPORTED to skip race tests

2017-02-27 12:17:53 +09:00