[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/0194-swift-parser-parseexprsequence.swift

@@ -0,0 +1,74 @@
+// 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
+
+protocol A {
+    typealias E
+}
+struct B<T : A> {
+    let h -> g {
+   d j d.i = {
+}
+ {
+   g) {
+        h  }
+}
+protocol f {
+   class func i()
+}
+class d: f{  class func i {}
+struct d<f : e,e where g.h == f.h> {
+}
+protocolias h
+}
+func some<S: SequenceType, T where Optional<T> == S.Generator.Element>(xs : S) -> T? {
+    for (mx : T?) in xs {
+        if let x? = mx {
+            return x
+        }
+    }
+    return nil
+}
+let xs : [Int?] = [nil, 4, nil]
+println(some(xs))
+fuotocol A {
+    typealias B
+}return []
+}
+func i(c: () -> ()) {
+}
+cnc c<d {
+    enum c {
+        func e
+        var _ = e
+    }
+}
+class A<T : A> {
+}
+func some<C -> b = b
+}
+protocol A {
+    typealias E
+}
+struct B<T : As a {
+    typealias b = b
+}
+func a<T>() {f {
+   class func i()
+}
+class d: f{  class func i {}
+func f() {
+    ({})
+}
+func prefix(with: String) -> <T>(() -> T) -> String {
+  return { g in "\(with): \(g())" }
+}
+protocol a : a {
+}
+var x1 = 1
+var f1: Int -> Int = {
+    return $0
+}
+let su a(2, 3)))