Run the following live tests: * aws-ec2: Tests run: 113, Failures: 5, Errors: 0, Skipped: 14 * digitalocean2: Tests run: 64, Failures: 2, Errors: 0, Skipped: 8
AWS tests are known ones that were considered low priority in previous discussions. The DigitalOcean failures are transient failures due to a VM that did not shutdown in the configured timeout and a subsequent test that assumes it in OFF state. I've also created a script to compare the source tarballs with the Git tag [1], to make sure the contents of the release are OK. It tkes as input the path tot he folder where all source tarballs are, and then validates them against the corresponding tag in each repo. Feel free to test/fix/modify/play with it. Currently the tarballs only contain the extra LICENSE, NOTICE, and DEPENDENCIES files that are auto-generated by our Maven build when performing a release. Apart from that all files match the tag, so we can consider the tarballs to be OK. I. [1] https://dist.apache.org/repos/dist/dev/jclouds/compare_tarball_tag.sh On 3 August 2015 at 23:50, Ignasi Barrera <n...@apache.org> wrote: >> +1 - lgtm! > > Should this go to the VOTE thread? > > On 3 August 2015 at 14:19, Andrew Bayer <andrew.ba...@gmail.com> wrote: >> +1 - lgtm! >> >> A. >> >> On Mon, Aug 3, 2015 at 10:39 AM, Ignasi Barrera <n...@apache.org> wrote: >> >>> I've just updated the fix version for the mentioned issues and the >>> release notes should be OK now. >>> Thanks for checking Arvind! >>> >>> On 2 August 2015 at 23:19, Andrew Phillips <andr...@apache.org> wrote: >>> >> can we mark them as fixed and update the annoucement? >>> > >>> > >>> > Luckily, since the VOTE thread only includes a link to JIRA (rather than >>> a >>> > list of the issues themselves), we shouldn't have to update the >>> announcement >>> > - just set the Fix Versions in JIRA correctly. >>> > >>> > Thanks for spotting that! >>> > >>> > Regards >>> > >>> > ap >>>
