Run container smoke checks on two-CPU runners - #3
Merged
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
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.
Private GitHub runners provide two CPUs, so requesting three CPUs prevents the deployment smoke test from starting. Cap the test's CPU limit to the Docker daemon's available capacity and allow a lower limit for reproducing CI locally. Deployment resource limits remain at three CPUs and 2 GiB.
Validation: bash syntax check passes; the published image passed offline startup, asset/key checks, restart, forced UI regeneration, and graceful shutdown with the migrated configuration at two CPUs and 2 GiB.