I've run the following live tests: aws-ec2: Tests run: 113, Failures: 8, Errors: 0, Skipped: 4 chef: Tests run: 59, Failures: 1, Errors: 0, Skipped: 10 enterprisechef: Tests run: 47, Failures: 0, Errors: 0, Skipped: 0 hpcloud-compute: Tests run: 69, Failures: 3, Errors: 0, Skipped: 6 cloudsigma2-lvs: Tests run: 78, Failures: 4, Errors: 0, Skipped: 10 digitalocean: Tests run: 57, Failures: 0, Errors: 0, Skipped: 0
The AWS failing tests are known issues. While planning the release we addressed the ones that affected the ComputeService abstraction, so the remaining tests shouldn't be considered blockers. The tests that fail in Chef are succeeding in Enterprise Chef, so they probably fail due to a configuration issue in my home Chef Server. Failed tests in HP Cloud are due to an unsupported "suspend node" invocation on an instance, and due to a change in their templates, where an Ubuntu 12 is expected and an Ubuntu 14 is returned. Shouldn't be blocker as it only affects the default template and users are able to configure that. CloudSigma test failures are in the compute service, where the "runScript" method can't connect to the deployed VMs. It is likely to be caused by the cloud image being used, as they have changed the images in the Marketplace and the old image we used in tests is no longer available. Regarding the verification script, it works for me. This is my build environment: nacx@maqui:~/src/asf/1.9.0-rc1/jclouds-labs-google-1.9.0 $ mvn -version Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T22:58:10+02:00) Maven home: /opt/maven Java version: 1.7.0_51, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.10.2", arch: "x86_64", family: "mac" On 17 March 2015 at 22:10, Shrinand Javadekar <shrin...@maginatics.com> wrote: > The verify_jclouds shell script fails with an error in GCE. That also > results in tests not running for Google Cloud Storage. > > Failed tests: > ParseUrlMapValidateTest>BaseParserTest.test:69 » HttpResponse Error > parsing in... > UrlMapApiMockTest.validate:115 » IllegalState Incorrect number of > names on @or... > > Nonetheless, I ran our own internal tests against several blobstores > (including Google) and they completed successfully. > > Results attached. > > -Shri > > > On Mon, Mar 16, 2015 at 3:27 PM, Shrinand Javadekar > <shrin...@maginatics.com> wrote: >> Thanks for doing this Ignassi. I'll test the RC bits against various >> blobstores and let you'll know how it goes. >> >> -Shri >> >> On Sun, Mar 15, 2015 at 1:59 PM, Ignasi Barrera <n...@apache.org> 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. >>> >>> Thank you.
