-
Notifications
You must be signed in to change notification settings - Fork 38.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using bigger node for minions for jenkin-e2e tests. #9678
Conversation
LGTM |
@@ -53,6 +54,7 @@ else | |||
export MASTER_SIZE=${MASTER_SIZE:-"t2.small"} | |||
else | |||
export MASTER_SIZE=${MASTER_SIZE:-"g1-small"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change to n1-standard-1 too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally agree. We should never be running on shared cores for CI e2e tests. It introduces unnecessary timing variability, which makes debugging more difficult.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our performance goals are phrased in the context of an n1-standard-4 master (#6454)
Done! |
Using bigger node for minions for jenkin-e2e tests.
GCE e2e build/test failed for commit a1065d1. |
cc/ @brendandburns @quinton-hoole
This is not a fix for #9312, but it should help us to rule out failure such as:
#9312 (comment)