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

Retry and eventually fail after timeouts, instead of ignoring. #94

Merged
merged 1 commit into from
Jul 11, 2019

Conversation

aomarks
Copy link
Member

@aomarks aomarks commented Jul 11, 2019

Fixes #86

Before, we simply ignored timeouts, allowing the sample size to fall by one each time. In the case that all samples timed out, this caused a hard crash in code that assumed there would be at least one measurement.

Now, we retry timeouts 3 times and abort after the final attempt.

This is what will now happen if your server is down:

Screen Shot 2019-07-11 at 10 55 35 AM

Before, we simply ignored timeouts, allowing the sample size to fall by
one each time. In the case that all samples timed out, this caused a
hard crash in code that assumed there would be at least one measurement.

Now, we retry timeouts 3 times and abort after the final attempt.
@aomarks aomarks requested a review from rictic July 11, 2019 17:56
Copy link
Member

@rictic rictic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, nice. This would have saved me repeatedly

@aomarks aomarks merged commit f70667d into master Jul 11, 2019
@aomarks aomarks deleted the result-crash branch July 11, 2019 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Crash on reporting results
2 participants