Im surprised to see this fail. It looks like it is a storage test that is unrelated. Ill do another push to trigger it again to see if it is a persistent problem.
One problem the most recent commit resolves is the TargetHttpProxyLiveTest. It tries to create the same UrlMap twice which is causing it to fail the second time. This was then leading to the resources not being deleted so the first test fails the next time. Warning there may be some resources out there on your project that are worth deleting! Another point of interest: UrlMapOptions are used for both Insert and Patch operations. This means sometimes name and defaultService are required (in the insert case) and sometimes they are not (in the patch case). I attempted to resolve this with two different well documented build options. Is this a good way to handle cases like this? Is this an improvement? WDYT? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/117#issuecomment-68011936
