mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
606ee29b74
The logic in 46b8ad3 to avoid putting certain diagnostics into
serialized diagnostic files only makes sense if
1. every diagnostic emitted in file A.swift while processing a
different file B.swift would be emitted if we processed A.swift on
its own
2. we actually do process A.swift on its own in the same build,
or have previously done an incremental build and produced the same
diagnostic
But the latter isn't actually guaranteed: if one batch job exits with
a failure status, the driver will exit as well, assuming there's no
point in continuing. Fortunately, we do have a flag that overrides
this behavior, -continue-building-after-errors.
(As noted in the patch, -continue-building-after-errors isn't *exactly*
what we want. But it's conservatively correct.)
20 lines
772 B
Swift
20 lines
772 B
Swift
// RUN: not %target-build-swift %S/Inputs/error.swift %s 2>&1 | %FileCheck %s
|
|
// RUN: not %target-build-swift -continue-building-after-errors %S/Inputs/error.swift %s 2>&1 | %FileCheck -check-prefix=CHECK-CONTINUE %s
|
|
|
|
// Check that batch mode implies -continue-building-after-errors.
|
|
// RUN: touch %t.empty.swift
|
|
// RUN: not %target-build-swift -enable-batch-mode -j2 %S/Inputs/error.swift %S/../Inputs/empty.swift %s %t.empty.swift 2>&1 | %FileCheck -check-prefix=CHECK-BATCH %s
|
|
|
|
// CHECK: self.bar = self.bar
|
|
// CHECK-NOT: self.baz = self.baz
|
|
// CHECK-CONTINUE: self.bar = self.bar
|
|
// CHECK-CONTINUE: self.baz = self.baz
|
|
// CHECK-BATCH-DAG: self.bar = self.bar
|
|
// CHECK-BATCH-DAG: self.baz = self.baz
|
|
struct Bar {
|
|
let baz: Int
|
|
init() {
|
|
self.baz = self.baz
|
|
}
|
|
}
|