[test] Don't run still-crashing compiler_crashers under no-asserts builds.

Per discussion on the list. From now on, when you fix a compiler_crashers
test case, move it to compiler_crashers_fixed so that we get no-asserts and
ASan coverage.

Swift SVN r27055

validation-test/compiler_crashers_fixed/0219-swift-module-isstdlibmodule.swift

@@ -0,0 +1,32 @@
+// RUN: not %target-swift-frontend %s -parse
+
+// Distributed under the terms of the MIT license
+// Test case submitted to project by https://github.com/practicalswift (practicalswift)
+// Test case found by fuzzing
+
+import Foundation
+class d<c>: NSObject {
+    var b: c
+    init(b: c) {
+        self.b = b
+   }
+}
+protocol l : p {
+}
+protoc l()
+}
+class o: p {
+    class func l() : f {
+}
+func h<d {
+    enum h {
+        func e
+        var _ = d:b class b
+struct l<e : SequenceType> {
+    l g: e
+}
+func h<e>() -> [l<, l: i) -> (((i, i) -> i) -> i) {
+    b {
+        (h -> i)  t: n>(s: t) {
+    s.i()
+>-> ())]