-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
improve test timeout in automation smoke tests #13182
Conversation
|
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.
👍
@@ -189,7 +189,7 @@ func SetupAutomationBasic(t *testing.T, nodeUpgrade bool) { | |||
g.Expect(counter.Int64()).Should(gomega.BeNumerically(">=", int64(expect)), | |||
"Expected consumer counter to be greater than %d, but got %d", expect, counter.Int64()) | |||
} | |||
}, "10m", "1s").Should(gomega.Succeed()) // ~1m for cluster setup, ~2m for performing each upkeep 5 times, ~2m buffer | |||
}, "5m", "1s").Should(gomega.Succeed()) // ~1m for cluster setup, ~2m for performing each upkeep 5 times, ~2m buffer |
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.
Not sure why this was bumped from 5
to 10
earlier. But 5
is more than enough.
@@ -1238,7 +1238,7 @@ func TestSetOffchainConfigWithMaxGasPrice(t *testing.T) { | |||
g.Expect(counter.Int64()).Should(gomega.BeNumerically(">", int64(0)), | |||
"Expected consumer counter to be greater than 0, but got %d") | |||
} | |||
}, "2m", "5s").Should(gomega.Succeed()) // ~1m for cluster setup, ~1m for performing each upkeep once, ~2m buffer | |||
}, "4m", "5s").Should(gomega.Succeed()) // ~1m for cluster setup, ~1m for performing each upkeep once, ~2m buffer |
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.
This test was flaky and failed multiple times at this step. Increasing wait period to 4m
resolves this flake.
Fixing test timeout issues that was seen during #12688