Skip to content
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

Merged
merged 1 commit into from
May 8, 2024

Conversation

KaloyanTanev
Copy link
Contributor

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

@KaloyanTanev KaloyanTanev requested a review from gsora May 8, 2024 13:31
@KaloyanTanev KaloyanTanev self-assigned this May 8, 2024
@KaloyanTanev KaloyanTanev changed the title Increase timeout of timeout test cmd: increase timeout of timeout test May 8, 2024
Copy link

codecov bot commented May 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.42%. Comparing base (3e41eba) to head (cb19eca).
Report is 1 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

@@ -96,7 +96,7 @@ func TestBeaconTest(t *testing.T) {
OutputToml: "",
Quiet: false,
TestCases: nil,
Timeout: time.Nanosecond,
Timeout: 5 * time.Nanosecond,
Copy link
Contributor

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. :)

Copy link
Contributor Author

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.

@KaloyanTanev KaloyanTanev force-pushed the kalo/charon-test-timeout-of-timeout-tests branch from e68cabc to cb19eca Compare May 8, 2024 13:52
Copy link

sonarcloud bot commented May 8, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@gsora gsora added the merge when ready Indicates bulldozer bot may merge when all checks pass label May 8, 2024
@obol-bulldozer obol-bulldozer bot merged commit 8e2e64a into main May 8, 2024
12 checks passed
@obol-bulldozer obol-bulldozer bot deleted the kalo/charon-test-timeout-of-timeout-tests branch May 8, 2024 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge when ready Indicates bulldozer bot may merge when all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants