[build-preset] Add no_test variants of all of the buildbot_linux_* pr… #20109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci smoke test |
|
preset=buildbot_linux_1604,notest |
|
Looks like, I can't use multiple mixins = (. |
|
Nope. I just messed up. |
…esets. The key thing is that these skip all testing except for the integration testing and thus are perfect for subproject buildbot testing. The reason why I am doing this is I discovered that dispatch is not using build-presets. This means that dispatch may not get updated properly (resulting in integration test failures) when we add new package installation dependencies (like llvm-cov, llvm-profdata) for the integration tests. This is functionally the same as dispatch's build today except that we /will/ build lldb. That being said I think it makes sense to build the entire package for dispatch so if we have any integration issues in between lldb and dispatch we can test them. SR-9080
gottesmm
force-pushed
the
pr-60b76bba625dd71797c6790a927e6b56081af615
branch
from
0e7e4db
to
d6323fb
Compare
|
preset=buildbot_linux_1604,notest |
1 similar comment
|
preset=buildbot_linux_1604,notest |
|
@swift-ci smoke test |
|
preset=buildbot_linux_1604,notest |
compnerd
approved these changes
Oct 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…esets.
The key thing is that these skip all testing except for the integration testing
and thus are perfect for subproject buildbot testing.
The reason why I am doing this is I discovered that dispatch is not using
build-presets. This means that dispatch may not get updated properly (resulting
in integration test failures) when we add new package installation dependencies
(like llvm-cov, llvm-profdata) for the integration tests.
This is functionally the same as dispatch's build today except that we /will/
build lldb. That being said I think it makes sense to build the entire package
for dispatch so if we have any integration issues in between lldb and dispatch
we can test them.
SR-9080