Jclouds builds on java 7, and tries to keep runtime compatibility with java 6 (via the animal sniffer plugin). We still don't use java 8, so I agree this shouldn't block the release, although we should track it in a JIRA.
More live test results: google-compute-engine: Tests run: 153, Failures: 1, Errors: 0, Skipped: 5 The failed test seems to be a transient failure due to a timeout: testOptionToNotBlock(org.jclouds.googlecomputeengine.compute.GoogleComputeEngineServiceLiveTest) Time elapsed: 229.849 sec <<< FAILURE! java.lang.AssertionError: duration(50) longer than expected(30) seconds! On 18 March 2015 at 00:40, Andrew Gaul <g...@apache.org> wrote: > On Tue, Mar 17, 2015 at 01:54:20PM -0700, Andrew Gaul wrote: >> On Sun, Mar 15, 2015 at 09:59:33PM +0100, Ignasi Barrera wrote: >> > This thread is for discussion of the first release candidate for >> > Apache jclouds 1.9.0. Please use this thread for discussion of issues >> > uncovered in the RC, questions you may have about the RC, etc. >> >> The verification script fails for me due to a unit test failure in >> google-compute-engine. I tried with a few variations of JDK 6, 7, and >> 8; any idea what I am doing wrong? >> >> I also attached a set of successful integration tests across all major >> object stores. We have two spurious failures for aws-s3 but otherwise >> we have more passing tests than ever! > > Ignasi suggested retesting with several Java versions. I found that > jdk1.8.0_25 and earlier pass the verification script but that > jdk1.8.0_31 and later fail. While this seems like a general > GSON/reflection issue, can someone familiar with GCE provider help > triage the severity of this? From my perspective this need not block > the release. > > -- > Andrew Gaul > http://gaul.org/
