Add an end-to-end test for the option to print compile jobs for module dependencies

[artemcm]

As discovered by invoking the fast dependency scanner from within the driver.

[DougGregor]

Thank you!

[artemcm]

@swift-ci test

[artemcm]

The test in this PR invokes the Fast Dependency Scanner (with -frontend -scan-dependencies). I suspect the CI failure is caused by the fact that the CI machine's toolchain does not yet have a sufficiently recent version of the compiler and therefore does not have the Fast Dependency Scanner. :(

[DougGregor]

The test in this PR invokes the Fast Dependency Scanner (with -frontend -scan-dependencies). I suspect the CI failure is caused by the fact that the CI machine's toolchain does not yet have a sufficiently recent version of the compiler and therefore does not have the Fast Dependency Scanner. :(

@shahmishal what is the process by which the toolchain gets updated for CI on this repo? We're doing some iteration with the main swift repo

[shahmishal]

It's using released compiler - Swift 5.2, I can update the job to use master nightly if that helps.

[artemcm]

That would help a lot for this and upcoming changes.

[DougGregor]

It's using released compiler - Swift 5.2, I can update the job to use master nightly if that helps.

That would be wonderful, thank you!

[DougGregor]

@swift-ci test

[artemcm]

@swift-ci test

[DougGregor]

@swift-ci test

[artemcm]

As I kept iterating on this, this PR and the test it adds got subsumed into: #113