-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
storage: TestRetryConformance failed #9178
storage: TestRetryConformance failed #9178
Comments
Test passed for commit 69c49f2 (Build Status, Sponge)! Closing this issue. |
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. commit: ec9b526 |
|
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 82054d0 |
Not sure why I originally closed this issue. Error from the latest comment is the same as above. |
^ Recently got this error as well. |
This is another retryable net.OpError that can arise when a connection has been closed. So far we've only seen this in TestRetryConformance cases rather than in customer issues, but there is no reason not to do a retry and we think it can cut down on flakes from this test. I'm going to do another PR to add this to google-api-go-client since it often occurs on uploads. Updates googleapis#9178
This is another retryable net.OpError that can arise when a connection has been closed. So far we've only seen this in TestRetryConformance cases rather than in customer issues, but there is no reason not to do a retry and we think it can cut down on flakes from this test. I'm going to do another PR to add this to google-api-go-client since it often occurs on uploads. Updates #9178
A few fixes to shouldRetry, which is used only for storage uploads. * Remove attempt to unwrap syscall errors and use string matching instead, as is used in the veneer client layer for storage. * Use errors.Is and appropriate sentinel for net.ErrClosed. * Add broken pipe error, which is causing flakes in veneer layer tests (see googleapis/google-cloud-go#10374 * Add unit test for shouldRetry. Closes googleapis/google-cloud-go#9178
* fix(storage): update shouldRetry for GCS uploads A few fixes to shouldRetry, which is used only for storage uploads. * Remove attempt to unwrap syscall errors and use string matching instead, as is used in the veneer client layer for storage. * Use errors.Is and appropriate sentinel for net.ErrClosed. * Add broken pipe error, which is causing flakes in veneer layer tests (see googleapis/google-cloud-go#10374 * Add unit test for shouldRetry. Closes googleapis/google-cloud-go#9178 * don't use xerrors
Beefed up retry logic for broken pipe errors in this repo and in apiary. We should see fewer flakes on this test especially once we pick up the new release of the apiary client. |
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 1e2af81 |
Latest failure should be fixed by the Apiary library patch as soon as we pick up the new release. |
Note: #8185 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: cae54ed
buildURL: Build Status, Sponge
status: failed
The text was updated successfully, but these errors were encountered: