Possible fix: https://github.com/jclouds/jclouds/pull/502
git log suggests that we have tweaked the behavior of zero-length requests several times; I appreciate feedback before merging. On Sat, Aug 09, 2014 at 01:24:58AM +0200, Andrew Phillips wrote: > We've had a bunch of hanging CI builds in DEV@clouds of late, > seemingly related to MockWebServer. Here's the most recent example > [1]: > > Starting test > testZeroLengthPutHasContentLengthHeader(org.jclouds.s3.S3ClientMockTest) > Aug 08, 2014 6:44:07 PM > com.squareup.okhttp.mockwebserver.MockWebServer$3 processOneRequest > INFO: Received request: PUT /bucket/someDir/fileName HTTP/1.1 and > responded: HTTP/1.1 200 OK > Aug 08, 2014 6:44:08 PM > com.squareup.okhttp.mockwebserver.MockWebServer$3 processOneRequest > INFO: Received request: PUT /bucket/object HTTP/1.1 and responded: > HTTP/1.1 200 OK > <hanging> > > Has anyone run across this before? > > Regards > > ap > > [1] https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1067/console -- Andrew Gaul http://gaul.org/
