Adapt Driver Dependencies Test Suite to Private Dependencies #31762
Conversation
|
@swift-ci smoke test |
|
The swiftdeps file includes a version at the top. How about incrementing that? |
|
You have my sympathy! There are a lot of tests to fix. |
|
We don't need to bump the version number just for private dependencies since the written format is independent of these changes. That is, unless you meant that it should have been incremented a-priori. In which case, I can do the grunt work for that in a follow-up just to make sure I get all the tests in one pass. |
|
Hm, this is the second time I've seen SourceKit/CodeComplete/complete_checkdeps_bridged.swift fail spuriously... @swift-ci clean smoke test Linux platform |
|
Good point about the format being compatible. I'm thinking, though, that even though we don't need to bump it, it could be useful to bump it. Might it offer an easy way to see which authoring strategy is being used in the frontend? For instance when we have to go in and look at a compiler that we didn't build? |
|
@swift-ci smoke test Linux |
|
⛵ |
No description provided.