CASMTRIAGE-7252: Increase DEFAULT_IMS_IMAGE_SIZE from 30 to 60 #143
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
mharding-hpe
force-pushed
the
casmtriage-7252
branch
2 times, most recently
from
425b08d
to
fbbf0a7
Compare
mharding-hpe
force-pushed
the
casmtriage-7252
branch
from
fbbf0a7
to
5ec9605
Compare
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.
CASMTRIAGE-7252 was opened because a CFS image customization session failed because the default IMS image size was too small. In an ideal world, this wouldn't happen because:
build_env_sizeto the IMS job that it creates.or
build_env_sizewas specified, IMS would try to determine a reasonable one based on the other parameters.However, both of those are obviously more complicated things to implement. So this PR takes the safer route of just increasing our default IMS image size to a value that does not hit the problem in question.