Skip to content

Commit 90baa46

Browse files
authored
Merge pull request #223 from artemcm/DocumentFrontendTesting
[Readme] Document flow of testing against tip-of-trunk frontend
2 parents 4ff755a + 736dc91 commit 90baa46

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,17 @@ $ SWIFT_DRIVER_ENABLE_INTEGRATION_TESTS=1 \
8888
swift test -c release --parallel
8989
```
9090

91+
#### Testing against `swift` compiler trunk
92+
`swift-driver` Continuous Integration runs against the most recent Trunk Development snapshot published at [swift.org/download](https://swift.org/download/).
93+
94+
When developing patches that have complex interactions with the underlying `swift` compiler frontend, it may be prudent to ensure that `swift-driver` tests also pass against the current tip-of-trunk `swift`. To do so, create an empty pull request against [github.com/apple/swift](https://github.com/apple/swift) and perform cross-repository testing against your `swift-driver` pull request #, for example:
95+
```
96+
Using:
97+
apple/swift-driver#208
98+
@swift-ci smoke test
99+
```
100+
@swift-ci cross-repository testing facilities are described [here](https://github.com/apple/swift/blob/master/docs/ContinuousIntegration.md#cross-repository-testing).
101+
91102
#### Preparing a Linux docker for debug
92103

93104
When developing on macOS without quick access to a Linux machine, using a Linux Docker is often helpful when debugging.

0 commit comments

Comments
 (0)