Launchable: Use Zero Input Subsetting #12650
Merged
Conversation
This file contains hidden or 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
ono-max
force-pushed
the
launchable-zero-input-subset2
branch
from
26f155c to
469a299
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Right now, Launchable web page shows the integration issue: “Too many files included in the subset output were not recorded”.
https://app.launchableinc.com/organizations/ruby/workspaces/ruby/actions/predictive-test-selection/analyze/test-sessions/3752503
The reason why the integration issue occurs is because we send all of tests including skipped tests as a subset input. To solve the problem, there are two solutions:
Using Zero Input Subsetting would be easier, so I'm gonna use Zero Input Subsetting.