-
Notifications
You must be signed in to change notification settings - Fork 84
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
cmd: increase timeout of timeout test #3079
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3079 +/- ##
==========================================
- Coverage 56.49% 56.42% -0.07%
==========================================
Files 208 208
Lines 29020 29018 -2
==========================================
- Hits 16395 16374 -21
- Misses 10805 10823 +18
- Partials 1820 1821 +1 ☔ View full report in Codecov by Sentry. |
cmd/testbeacon_internal_test.go
Outdated
@@ -96,7 +96,7 @@ func TestBeaconTest(t *testing.T) { | |||
OutputToml: "", | |||
Quiet: false, | |||
TestCases: nil, | |||
Timeout: time.Nanosecond, | |||
Timeout: 5 * time.Nanosecond, |
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.
It's your business but to me this is the first indicator of potentially flakey test. :)
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.
Looks a bit weird indeed, but I want to have some timeout that is triggered before my HTTP call succeeds... Currently this test will falsely fail on 2 occasions:
- If the http call is blazing fast (<100ns), but that is impossible I believe
- If the code executes slower in some go routines and it doesn't reach the step of registering all the targets it needs to call (what happened before). I've bumped it to 100ns now. Seems highly unlikely the code doesn't execute for 2 targets for 100ns, as it was executing for 1ns for 2 targets in all of the runs except this last one up until now.
e68cabc
to
cb19eca
Compare
Quality Gate passedIssues Measures |
Sometimes timeout is so little that the test doesn't even reach the second instance, as observed in the pipeline here.
category: bug
ticket: none