Closed
Description
After merging #211 travis build for oraclejdk7
failed with an error in ITStorageTest.testUpdate
:
testUpdateBlob(com.google.gcloud.storage.ITStorageTest) Time elapsed: 10.421 sec <<< ERROR!
com.google.gcloud.storage.StorageException: Backend Error
at com.google.api.client.googleapis.json.GoogleJsonResponseException.from(GoogleJsonResponseException.java:145)
at com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:113)
at com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:40)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest$1.interceptResponse(AbstractGoogleClientRequest.java:321)
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1056)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:419)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:352)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:469)
at com.google.gcloud.spi.DefaultStorageRpc.patch(DefaultStorageRpc.java:231)
at com.google.gcloud.storage.StorageImpl$11.call(StorageImpl.java:343)
at com.google.gcloud.storage.StorageImpl$11.call(StorageImpl.java:340)
at com.google.gcloud.RetryHelper.doRetry(RetryHelper.java:181)
at com.google.gcloud.RetryHelper.runWithRetries(RetryHelper.java:247)
at com.google.gcloud.RetryHelper.runWithRetries(RetryHelper.java:237)
at com.google.gcloud.storage.StorageImpl.update(StorageImpl.java:340)
at com.google.gcloud.storage.ITStorageTest.testUpdateBlob(ITStorageTest.java:150)
I never experienced this error locally and it seems not to occur always (builds for other java versions and next builds succeeded). The error message Backend Error
makes me think that the problem resides outside of our library. I open this issue just to double check with you guys, can we consider this as a sporadic error?