Here are more live test results: chef: ests run: 63, Failures: 1, Errors: 0, Skipped: 27 enterprisechef: Tests run: 47, Failures: 0, Errors: 0, Skipped: 0 digitalocean: Tests run: 57, Failures: 5, Errors: 0, Skipped: 13 cloudsigma2-lvs: Tests run: 50, Failures: 1, Errors: 0, Skipped: 0 elastichosts-lon-b: Tests run: 150, Failures: 1, Errors: 0, Skipped: 9
The failed and skipped tests in Chef are in the deprecated TransientChef, which has already been removed from master. It is legacy code that has already been removed, so can be perfectly ignored. The DigitalOcean tests fail because the images used in the live tests don't exist in all regions. I've fixed that here [1] and all live tests pass. It is just a test config but the provider works well. The failed test in ElasticHosts is due to a test configuration too. The provider name is "elastichosts-lon-b", and the dashes cause the default group naming convention to not assign the group name properly. This is something that can be changed in the tests, as they use the provider id for the group name. Again, is just test configuration and the provider works well. [1] https://github.com/jclouds/jclouds-labs/pull/93 On 16 October 2014 22:34, Shrinand Javadekar <shrin...@maginatics.com> wrote: > On Mon, Oct 13, 2014 at 10:11 AM, Shrinand Javadekar > <shrin...@maginatics.com> wrote: >> I'll run live tests against various blobstore and send feedback, logs, etc. > > Unfortunately, I have several other higher priority tasks to care of > and won't be able to run these tests this week. > > -Shri > >> >> On Sun, Oct 12, 2014 at 12:13 PM, Andrew Phillips <aphill...@qrmedia.com> >> wrote: >>> This thread is for discussion of the first release candidate for >>> Apache jclouds 1.8.1. Please use this thread for discussion of issues >>> uncovered in the RC, >>> questions you may have about the RC, etc. Thank you. Regards ap
