You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Ignasi Barrera <na...@apache.org> on 2017/11/26 00:13:15 UTC
[DISCUSS] Release Apache jclouds 2.0.3 RC1
This thread is for discussion of the first release candidate for
Apache jclouds 2.0.3.
Please use this thread for discussion of issues uncovered in the RC,
questions you may have about the RC, etc.
If you want to help to validate the release, you'll find the following
scripts here [1]:
* verify_jclouds_rc.sh - This will build the RC, run all tests, run
the Apache RAT checks and verify the signatures.
* compare_tarball_tag.sh - This will compare the contents of the RC
tarballs with the source repo tags.
You can also go run live tests for your preferred providers and post
the results here, or use the projects in the jclouds-examples repo
[1], such as the "compute-basics" to rapidly smoke test the providers
you are interested in.
Thank you.
[1] https://dist.apache.org/repos/dist/dev/jclouds/
[2] https://github.com/jclouds/jclouds-examples
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Andrew Gaul <ga...@apache.org>.
Successfully ran verification script and integration tests against
atmos, aws-s3, b2, filesystem, google-cloud-storage,
rackspace-cloudfiles-us, and transient. Testing revealed one unexpected
failing B2 test and two GCS tests which are test-only issues which
master fixes.
On Sun, Nov 26, 2017 at 01:13:15AM +0100, Ignasi Barrera wrote:
> This thread is for discussion of the first release candidate for
> Apache jclouds 2.0.3.
> Please use this thread for discussion of issues uncovered in the RC,
> questions you may have about the RC, etc.
>
> If you want to help to validate the release, you'll find the following
> scripts here [1]:
>
> * verify_jclouds_rc.sh - This will build the RC, run all tests, run
> the Apache RAT checks and verify the signatures.
> * compare_tarball_tag.sh - This will compare the contents of the RC
> tarballs with the source repo tags.
>
> You can also go run live tests for your preferred providers and post
> the results here, or use the projects in the jclouds-examples repo
> [1], such as the "compute-basics" to rapidly smoke test the providers
> you are interested in.
>
>
> Thank you.
>
>
>
> [1] https://dist.apache.org/repos/dist/dev/jclouds/
> [2] https://github.com/jclouds/jclouds-examples
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Ignasi Barrera <na...@apache.org>.
Thanks, Andrea. A couple things:
1. You are building it with Java 8, which is not "officially"
supported. Can you try building all this with Java 7? Let's see if it
fails with Java 7 (I think it should work).
2. You replied to the DISCUSS thread, not the VOTE thread. Once you
test it with the proper Java version, please, post your feedback in
the right thread :)
Thanks for trying so quickly!
On 26 November 2017 at 11:24, Andrea Turli <an...@gmail.com> wrote:
> Successfully ran the verify script that checks
>
> - Download links work.
> - Binaries work.
> - Checksums and PGP signatures are valid.
> - Expanded source archive matches contents of RC tag.
> - Expanded source archive builds and passes tests.
>
> using
>
> $ mvn -v
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T09:58:13+02:00)
> Maven home: /usr/local/Cellar/maven/3.5.2/libexec
> Java version: 1.8.0_152, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/jre
> Default locale: en_IT, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>
> ---
>
> From my tests, there are problems with `jclouds-karaf` Integration tests
> module
>
> Results :
>
> Failed tests:
> testVagrant:org.jclouds.karaf.itests.ApisFeaturesInstallationTest.testVagrant:KarafTestContainer{mvn:org.apache.karaf\/apache-karaf\/2.3.11\/tar.gz}(org.jclouds.karaf.itests.ApisFeaturesInstallationTest):
> Expected jclouds-vagrant feature to be installed.
>
> Tests run: 59, Failures: 1, Errors: 0, Skipped: 1
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache jclouds :: Karaf ............................ SUCCESS [
> 1.574 s]
> [INFO] jclouds :: Karaf :: Core ........................... SUCCESS [
> 1.830 s]
> [INFO] jclouds :: Karaf :: Bundles ........................ SUCCESS [
> 0.039 s]
> [INFO] jclouds :: Karaf :: JSch Agentproxy for JSch (shaded bundle) SUCCESS
> [ 1.313 s]
> [INFO] jclouds :: Karaf :: Utils .......................... SUCCESS [
> 0.442 s]
> [INFO] jclouds :: Karaf :: Recipe ......................... SUCCESS [
> 0.318 s]
> [INFO] jclouds :: Karaf :: Cache .......................... SUCCESS [
> 0.385 s]
> [INFO] jclouds :: Karaf :: Services ....................... SUCCESS [
> 1.143 s]
> [INFO] jclouds :: Karaf :: Commands ....................... SUCCESS [
> 1.391 s]
> [INFO] jclouds :: Karaf :: URL Handler .................... SUCCESS [
> 0.301 s]
> [INFO] jclouds :: Karaf :: Chef ........................... SUCCESS [
> 0.033 s]
> [INFO] jclouds :: Karaf :: Chef :: Core ................... SUCCESS [
> 0.206 s]
> [INFO] jclouds :: Karaf :: Chef :: Services ............... SUCCESS [
> 0.368 s]
> [INFO] jclouds :: Karaf :: Chef :: Commands ............... SUCCESS [
> 0.620 s]
> [INFO] jclouds :: Karaf :: Chef :: Cache .................. SUCCESS [
> 0.254 s]
> [INFO] jclouds :: Karaf :: Feature ........................ SUCCESS [
> 0.829 s]
> [INFO] jclouds :: Karaf :: Integration Tests .............. FAILURE [03:54
> min]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 04:06 min
> [INFO] Finished at: 2017-11-26T10:50:05+01:00
> [INFO] Final Memory: 69M/835M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on
> project itests: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /Users/andrea/Desktop/2.0.3-rc1/jclouds-karaf-2.0.3/itests/target/surefire-reports
> for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :itests
>
> I think this has been fixed in master by gnodet in May but his commits have
> not been back-ported to 2.0.x branch, namely those are
> 7e7f9cea42068cac519abf6b03c27fdac35e990b
> 1d96d88b672ed1755251580d0e21f0e00504ee5a
> 18f0d03c4e18a7e4ef102d99fe1d4cb0d3857e16
> 15d2f9992a98d7712dc420825206bab01b55d20f
>
> ---
> For the reasons above, my vote is -1 as I think it would be better to fix
> jclouds-karaf and cut a RC2.
>
> Best,
> Andrea
>
> On Sun, Nov 26, 2017 at 1:13 AM, Ignasi Barrera <na...@apache.org> wrote:
>
>> This thread is for discussion of the first release candidate for
>> Apache jclouds 2.0.3.
>> Please use this thread for discussion of issues uncovered in the RC,
>> questions you may have about the RC, etc.
>>
>> If you want to help to validate the release, you'll find the following
>> scripts here [1]:
>>
>> * verify_jclouds_rc.sh - This will build the RC, run all tests, run
>> the Apache RAT checks and verify the signatures.
>> * compare_tarball_tag.sh - This will compare the contents of the RC
>> tarballs with the source repo tags.
>>
>> You can also go run live tests for your preferred providers and post
>> the results here, or use the projects in the jclouds-examples repo
>> [1], such as the "compute-basics" to rapidly smoke test the providers
>> you are interested in.
>>
>>
>> Thank you.
>>
>>
>>
>> [1] https://dist.apache.org/repos/dist/dev/jclouds/
>> [2] https://github.com/jclouds/jclouds-examples
>>
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Andrea Turli <an...@gmail.com>.
Successfully ran the verify script that checks
- Download links work.
- Binaries work.
- Checksums and PGP signatures are valid.
- Expanded source archive matches contents of RC tag.
- Expanded source archive builds and passes tests.
using
$ mvn -v
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T09:58:13+02:00)
Maven home: /usr/local/Cellar/maven/3.5.2/libexec
Java version: 1.8.0_152, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/jre
Default locale: en_IT, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
---
From my tests, there are problems with `jclouds-karaf` Integration tests
module
Results :
Failed tests:
testVagrant:org.jclouds.karaf.itests.ApisFeaturesInstallationTest.testVagrant:KarafTestContainer{mvn:org.apache.karaf\/apache-karaf\/2.3.11\/tar.gz}(org.jclouds.karaf.itests.ApisFeaturesInstallationTest):
Expected jclouds-vagrant feature to be installed.
Tests run: 59, Failures: 1, Errors: 0, Skipped: 1
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache jclouds :: Karaf ............................ SUCCESS [
1.574 s]
[INFO] jclouds :: Karaf :: Core ........................... SUCCESS [
1.830 s]
[INFO] jclouds :: Karaf :: Bundles ........................ SUCCESS [
0.039 s]
[INFO] jclouds :: Karaf :: JSch Agentproxy for JSch (shaded bundle) SUCCESS
[ 1.313 s]
[INFO] jclouds :: Karaf :: Utils .......................... SUCCESS [
0.442 s]
[INFO] jclouds :: Karaf :: Recipe ......................... SUCCESS [
0.318 s]
[INFO] jclouds :: Karaf :: Cache .......................... SUCCESS [
0.385 s]
[INFO] jclouds :: Karaf :: Services ....................... SUCCESS [
1.143 s]
[INFO] jclouds :: Karaf :: Commands ....................... SUCCESS [
1.391 s]
[INFO] jclouds :: Karaf :: URL Handler .................... SUCCESS [
0.301 s]
[INFO] jclouds :: Karaf :: Chef ........................... SUCCESS [
0.033 s]
[INFO] jclouds :: Karaf :: Chef :: Core ................... SUCCESS [
0.206 s]
[INFO] jclouds :: Karaf :: Chef :: Services ............... SUCCESS [
0.368 s]
[INFO] jclouds :: Karaf :: Chef :: Commands ............... SUCCESS [
0.620 s]
[INFO] jclouds :: Karaf :: Chef :: Cache .................. SUCCESS [
0.254 s]
[INFO] jclouds :: Karaf :: Feature ........................ SUCCESS [
0.829 s]
[INFO] jclouds :: Karaf :: Integration Tests .............. FAILURE [03:54
min]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 04:06 min
[INFO] Finished at: 2017-11-26T10:50:05+01:00
[INFO] Final Memory: 69M/835M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on
project itests: There are test failures.
[ERROR]
[ERROR] Please refer to
/Users/andrea/Desktop/2.0.3-rc1/jclouds-karaf-2.0.3/itests/target/surefire-reports
for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :itests
I think this has been fixed in master by gnodet in May but his commits have
not been back-ported to 2.0.x branch, namely those are
7e7f9cea42068cac519abf6b03c27fdac35e990b
1d96d88b672ed1755251580d0e21f0e00504ee5a
18f0d03c4e18a7e4ef102d99fe1d4cb0d3857e16
15d2f9992a98d7712dc420825206bab01b55d20f
---
For the reasons above, my vote is -1 as I think it would be better to fix
jclouds-karaf and cut a RC2.
Best,
Andrea
On Sun, Nov 26, 2017 at 1:13 AM, Ignasi Barrera <na...@apache.org> wrote:
> This thread is for discussion of the first release candidate for
> Apache jclouds 2.0.3.
> Please use this thread for discussion of issues uncovered in the RC,
> questions you may have about the RC, etc.
>
> If you want to help to validate the release, you'll find the following
> scripts here [1]:
>
> * verify_jclouds_rc.sh - This will build the RC, run all tests, run
> the Apache RAT checks and verify the signatures.
> * compare_tarball_tag.sh - This will compare the contents of the RC
> tarballs with the source repo tags.
>
> You can also go run live tests for your preferred providers and post
> the results here, or use the projects in the jclouds-examples repo
> [1], such as the "compute-basics" to rapidly smoke test the providers
> you are interested in.
>
>
> Thank you.
>
>
>
> [1] https://dist.apache.org/repos/dist/dev/jclouds/
> [2] https://github.com/jclouds/jclouds-examples
>
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Ignasi Barrera <na...@apache.org>.
Just FTR, the DigitalOcean tests will be fixed in the next release:
https://github.com/jclouds/jclouds/pull/1161
On 27 November 2017 at 20:28, Ignasi Barrera <na...@apache.org> wrote:
> I've verified the aws-ec2 provider with the compute-basics tool from
> jclouds-example and successfully created nodes, run scripts, listed images
> and deleted them.
>
> I've Also verified the jclouds CLI and the persistent compute services
> from the interactive karaf version.
>
> And here are the results of the live tests I've run:
> chef: Tests run: 66, Failures: 0, Errors: 0, Skipped: 0 (Total time: 2:15
> m)
> azurecompute-arm: Tests run: 151, Failures: 1, Errors: 0, Skipped: 2
> (Total time: 02:58 h)
> digitalocean2: Tests run: 67, Failures: 1, Errors: 0, Skipped: 10 (Total
> time: 20:50 m)
> packet: Tests run: 53, Failures: 0, Errors: 0, Skipped: 0 (Total time:
> 01:02 h)
>
> The digitalocean2 failures are the same ones spotted in the previous
> release. A misconfiguration in the test picks a wrong hardware profile and
> the creation of the initial droplet fails, making all subsequent tests in
> the class to be skipped. The API works, though, as all compute service
> tests succeed, so it is only a matter of a wrong test setup.
>
> In Azure there is one single failure to investigate related tot he metrics
> API, nothing to consider blocker. The skipped tests are expected as they
> are about configurations not supported by the Azure ARM security group
> extension.
>
>
> == Stacktraces ==
>
> azurecompute-arm:
>
> listVirtualMachineMetrics(org.jclouds.azurecompute.arm.features.MetricsApiLiveTest)
> Time elapsed: 43.624 sec <<< FAILURE!
> java.lang.AssertionError: expected [1] but found [0]
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:494)
> at org.testng.Assert.assertEquals(Assert.java:123)
> at org.testng.Assert.assertEquals(Assert.java:370)
> at org.testng.Assert.assertEquals(Assert.java:380)
> at org.jclouds.azurecompute.arm.features.MetricsApiLiveTest.
> listVirtualMachineMetrics(MetricsApiLiveTest.java:130)
>
> digitalocean2:
>
> testCreate(org.jclouds.digitalocean2.features.DropletApiLiveTest) Time
> elapsed: 0.985 sec <<< FAILURE!
> org.jclouds.http.HttpResponseException: command: POST
> https://api.digitalocean.com/v2/droplets HTTP/1.1 failed with response:
> HTTP/1.1 422 Unprocessable Entity; content: [{"id":"unprocessable_entity","message":"Cannot
> create a droplet with a smaller disk (20GB) than the image (30GB)."}]
> at org.jclouds.digitalocean2.handlers.DigitalOcean2ErrorHandler.
> handleError(DigitalOcean2ErrorHandler.java:43)
> at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(
> DelegatingErrorHandler.java:65)
> at org.jclouds.http.internal.BaseHttpCommandExecutorService
> .shouldContinue(BaseHttpCommandExecutorService.java:140)
> at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(
> BaseHttpCommandExecutorService.java:109)
> at org.jclouds.rest.internal.InvokeHttpMethod.invoke(
> InvokeHttpMethod.java:90)
> at org.jclouds.rest.internal.InvokeHttpMethod.apply(
> InvokeHttpMethod.java:73)
> at org.jclouds.rest.internal.InvokeHttpMethod.apply(
> InvokeHttpMethod.java:44)
> at org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.
> handleInvocation(FunctionalReflection.java:117)
> at com.google.common.reflect.AbstractInvocationHandler.invoke(
> AbstractInvocationHandler.java:87)
> at com.sun.proxy.$Proxy79.create(Unknown Source)
> at org.jclouds.digitalocean2.features.DropletApiLiveTest.
> testCreate(DropletApiLiveTest.java:75)
>
>
> On 27 November 2017 at 14:20, Ignasi Barrera <na...@apache.org> wrote:
>
>> Andrew, regarding the test, I'd say an input string for each OS would
>> make sense. @gaul, WDYT?
>> Regarding the release, if this is just about the test configuration but
>> not the behavior of the filesystem API itself, I'd say we should not block
>> the release for this reason?
>>
>> @andrea, thanks for running it on Java 7. May you post your vote by
>> replying to the [VOTE] thread? It is a PITA that Gmail collapses both
>> threads as one. One way to see the threads properly is to temporarily go to
>> the Gmail settings, and turn the conversation view off.
>> Regarding the failure in Java 8, I think it is some configuration in the
>> vagrant-java-bindings library we use. Perhaps @neykov can help here?
>>
>> *Caused by: org.osgi.framework.BundleException: Unresolved constraint in
>> bundle name.neykov.vagrant-java-bindings [87]: Unable to resolve 87.0:
>> missing requirement [87.0] osgi.ee <http://osgi.ee>; (&(osgi.ee
>> <http://osgi.ee>=JavaSE)(version=1.6))*
>>
>>
>> On 26 November 2017 at 21:35, Andrea Turli <an...@gmail.com>
>> wrote:
>>
>>> hi,
>>>
>>> I've just rebuilt with java 7
>>>
>>> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
>>> 2017-10-18T07:58:13Z)
>>> Maven home: /usr/share/maven
>>> Java version: 1.7.0_151, vendor: Oracle Corporation
>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>> Default locale: en, platform encoding: UTF-8
>>> OS name: "linux", version: "4.9.44-linuxkit-aufs", arch: "amd64", family:
>>> "unix"
>>>
>>> and jclouds-karaf has no issues
>>>
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache jclouds :: Karaf ............................ SUCCESS [
>>> 46.836 s]
>>> [INFO] jclouds :: Karaf :: Core ........................... SUCCESS [
>>> 5.985 s]
>>> [INFO] jclouds :: Karaf :: Bundles ........................ SUCCESS [
>>> 0.172 s]
>>> [INFO] jclouds :: Karaf :: JSch Agentproxy for JSch (shaded bundle)
>>> SUCCESS
>>> [ 5.848 s]
>>> [INFO] jclouds :: Karaf :: Utils .......................... SUCCESS [
>>> 2.720 s]
>>> [INFO] jclouds :: Karaf :: Recipe ......................... SUCCESS [
>>> 2.926 s]
>>> [INFO] jclouds :: Karaf :: Cache .......................... SUCCESS [
>>> 3.302 s]
>>> [INFO] jclouds :: Karaf :: Services ....................... SUCCESS [
>>> 7.548 s]
>>> [INFO] jclouds :: Karaf :: Commands ....................... SUCCESS [
>>> 13.752 s]
>>> [INFO] jclouds :: Karaf :: URL Handler .................... SUCCESS [
>>> 2.393 s]
>>> [INFO] jclouds :: Karaf :: Chef ........................... SUCCESS [
>>> 0.370 s]
>>> [INFO] jclouds :: Karaf :: Chef :: Core ................... SUCCESS [
>>> 1.955 s]
>>> [INFO] jclouds :: Karaf :: Chef :: Services ............... SUCCESS [
>>> 4.195 s]
>>> [INFO] jclouds :: Karaf :: Chef :: Commands ............... SUCCESS [
>>> 8.073 s]
>>> [INFO] jclouds :: Karaf :: Chef :: Cache .................. SUCCESS [
>>> 2.842 s]
>>> [INFO] jclouds :: Karaf :: Feature ........................ SUCCESS [
>>> 7.439 s]
>>> [INFO] jclouds :: Karaf :: Integration Tests .............. SUCCESS
>>> [17:05
>>> min]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 19:04 min
>>> [INFO] Finished at: 2017-11-26T20:28:31Z
>>> [INFO] Final Memory: 42M/280M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>>
>>> I change my vote to +1
>>>
>>> On Sun, Nov 26, 2017 at 9:20 PM, Andrew Phillips <ap...@qrmedia.com>
>>> wrote:
>>>
>>> > Please use this thread for discussion of issues uncovered in the RC,
>>> >> questions you may have about the RC, etc.
>>> >>
>>> >
>>> > The following test fails repeatedly for me on Windows:
>>> >
>>> > Failed tests:
>>> > FilesystemStorageStrategyImplTest.testDeletingInvalidPathFil
>>> > eEndsNormally:695
>>> > Deleting an invalid path ended with an InvalidPathException.
>>> >
>>> > Specifically, it's the "/" character in the test input "A<!:!@#$%^&*?]8
>>> > /\0"; removing that works.
>>> >
>>> > Would having an OS-specific test input seem like the correct solution?
>>> Or
>>> > should the test be modified to expect a test failure on Windows?
>>> >
>>> > Regards
>>> >
>>> > ap
>>> >
>>>
>>
>>
>
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Ignasi Barrera <na...@apache.org>.
I've verified the aws-ec2 provider with the compute-basics tool from
jclouds-example and successfully created nodes, run scripts, listed images
and deleted them.
I've Also verified the jclouds CLI and the persistent compute services from
the interactive karaf version.
And here are the results of the live tests I've run:
chef: Tests run: 66, Failures: 0, Errors: 0, Skipped: 0 (Total time: 2:15 m)
azurecompute-arm: Tests run: 151, Failures: 1, Errors: 0, Skipped: 2 (Total
time: 02:58 h)
digitalocean2: Tests run: 67, Failures: 1, Errors: 0, Skipped: 10 (Total
time: 20:50 m)
packet: Tests run: 53, Failures: 0, Errors: 0, Skipped: 0 (Total time:
01:02 h)
The digitalocean2 failures are the same ones spotted in the previous
release. A misconfiguration in the test picks a wrong hardware profile and
the creation of the initial droplet fails, making all subsequent tests in
the class to be skipped. The API works, though, as all compute service
tests succeed, so it is only a matter of a wrong test setup.
In Azure there is one single failure to investigate related tot he metrics
API, nothing to consider blocker. The skipped tests are expected as they
are about configurations not supported by the Azure ARM security group
extension.
== Stacktraces ==
azurecompute-arm:
listVirtualMachineMetrics(org.jclouds.azurecompute.arm.features.MetricsApiLiveTest)
Time elapsed: 43.624 sec <<< FAILURE!
java.lang.AssertionError: expected [1] but found [0]
at org.testng.Assert.fail(Assert.java:94)
at org.testng.Assert.failNotEquals(Assert.java:494)
at org.testng.Assert.assertEquals(Assert.java:123)
at org.testng.Assert.assertEquals(Assert.java:370)
at org.testng.Assert.assertEquals(Assert.java:380)
at
org.jclouds.azurecompute.arm.features.MetricsApiLiveTest.listVirtualMachineMetrics(MetricsApiLiveTest.java:130)
digitalocean2:
testCreate(org.jclouds.digitalocean2.features.DropletApiLiveTest) Time
elapsed: 0.985 sec <<< FAILURE!
org.jclouds.http.HttpResponseException: command: POST
https://api.digitalocean.com/v2/droplets HTTP/1.1 failed with response:
HTTP/1.1 422 Unprocessable Entity; content:
[{"id":"unprocessable_entity","message":"Cannot create a droplet with a
smaller disk (20GB) than the image (30GB)."}]
at
org.jclouds.digitalocean2.handlers.DigitalOcean2ErrorHandler.handleError(DigitalOcean2ErrorHandler.java:43)
at
org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:65)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:140)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:109)
at
org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
at
org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
at
org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
at
org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:117)
at
com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:87)
at com.sun.proxy.$Proxy79.create(Unknown Source)
at
org.jclouds.digitalocean2.features.DropletApiLiveTest.testCreate(DropletApiLiveTest.java:75)
On 27 November 2017 at 14:20, Ignasi Barrera <na...@apache.org> wrote:
> Andrew, regarding the test, I'd say an input string for each OS would make
> sense. @gaul, WDYT?
> Regarding the release, if this is just about the test configuration but
> not the behavior of the filesystem API itself, I'd say we should not block
> the release for this reason?
>
> @andrea, thanks for running it on Java 7. May you post your vote by
> replying to the [VOTE] thread? It is a PITA that Gmail collapses both
> threads as one. One way to see the threads properly is to temporarily go to
> the Gmail settings, and turn the conversation view off.
> Regarding the failure in Java 8, I think it is some configuration in the
> vagrant-java-bindings library we use. Perhaps @neykov can help here?
>
> *Caused by: org.osgi.framework.BundleException: Unresolved constraint in
> bundle name.neykov.vagrant-java-bindings [87]: Unable to resolve 87.0:
> missing requirement [87.0] osgi.ee <http://osgi.ee>; (&(osgi.ee
> <http://osgi.ee>=JavaSE)(version=1.6))*
>
>
> On 26 November 2017 at 21:35, Andrea Turli <an...@gmail.com> wrote:
>
>> hi,
>>
>> I've just rebuilt with java 7
>>
>> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
>> 2017-10-18T07:58:13Z)
>> Maven home: /usr/share/maven
>> Java version: 1.7.0_151, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>> Default locale: en, platform encoding: UTF-8
>> OS name: "linux", version: "4.9.44-linuxkit-aufs", arch: "amd64", family:
>> "unix"
>>
>> and jclouds-karaf has no issues
>>
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache jclouds :: Karaf ............................ SUCCESS [
>> 46.836 s]
>> [INFO] jclouds :: Karaf :: Core ........................... SUCCESS [
>> 5.985 s]
>> [INFO] jclouds :: Karaf :: Bundles ........................ SUCCESS [
>> 0.172 s]
>> [INFO] jclouds :: Karaf :: JSch Agentproxy for JSch (shaded bundle)
>> SUCCESS
>> [ 5.848 s]
>> [INFO] jclouds :: Karaf :: Utils .......................... SUCCESS [
>> 2.720 s]
>> [INFO] jclouds :: Karaf :: Recipe ......................... SUCCESS [
>> 2.926 s]
>> [INFO] jclouds :: Karaf :: Cache .......................... SUCCESS [
>> 3.302 s]
>> [INFO] jclouds :: Karaf :: Services ....................... SUCCESS [
>> 7.548 s]
>> [INFO] jclouds :: Karaf :: Commands ....................... SUCCESS [
>> 13.752 s]
>> [INFO] jclouds :: Karaf :: URL Handler .................... SUCCESS [
>> 2.393 s]
>> [INFO] jclouds :: Karaf :: Chef ........................... SUCCESS [
>> 0.370 s]
>> [INFO] jclouds :: Karaf :: Chef :: Core ................... SUCCESS [
>> 1.955 s]
>> [INFO] jclouds :: Karaf :: Chef :: Services ............... SUCCESS [
>> 4.195 s]
>> [INFO] jclouds :: Karaf :: Chef :: Commands ............... SUCCESS [
>> 8.073 s]
>> [INFO] jclouds :: Karaf :: Chef :: Cache .................. SUCCESS [
>> 2.842 s]
>> [INFO] jclouds :: Karaf :: Feature ........................ SUCCESS [
>> 7.439 s]
>> [INFO] jclouds :: Karaf :: Integration Tests .............. SUCCESS [17:05
>> min]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 19:04 min
>> [INFO] Finished at: 2017-11-26T20:28:31Z
>> [INFO] Final Memory: 42M/280M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
>> I change my vote to +1
>>
>> On Sun, Nov 26, 2017 at 9:20 PM, Andrew Phillips <ap...@qrmedia.com>
>> wrote:
>>
>> > Please use this thread for discussion of issues uncovered in the RC,
>> >> questions you may have about the RC, etc.
>> >>
>> >
>> > The following test fails repeatedly for me on Windows:
>> >
>> > Failed tests:
>> > FilesystemStorageStrategyImplTest.testDeletingInvalidPathFil
>> > eEndsNormally:695
>> > Deleting an invalid path ended with an InvalidPathException.
>> >
>> > Specifically, it's the "/" character in the test input "A<!:!@#$%^&*?]8
>> > /\0"; removing that works.
>> >
>> > Would having an OS-specific test input seem like the correct solution?
>> Or
>> > should the test be modified to expect a test failure on Windows?
>> >
>> > Regards
>> >
>> > ap
>> >
>>
>
>
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Jim Spring <jm...@gmail.com>.
Ignasi -
The failed tests are below.
I ran with the same command line flags you were. I'll rerun each set
below individually and see if any errors persist.
-jim
Failed tests:
MetricDefinitionsApiLiveTest.setupContext:89 null
MetricsApiLiveTest.setupContext:98 null
LoadBalancerApiLiveTest.testAttachNodesToBackendPool:250->createVirtualMachinesInGroupAndGetNicRefs:355
» RunNodes
ImageApiLiveTest.testCreateImage:116 » RunNodes error running 1 node
group(ima...
AzureComputeSecurityGroupExtensionLiveTest>BaseSecurityGroupExtensionLiveTest.testSecurityGroupCacheInvalidatedWhenDeletedExternally:422
» IllegalArgument
AzureComputeSecurityGroupExtensionLiveTest.testCreateNodeWithInboundPorts:121
» RunNodes
AzureComputeSecurityGroupExtensionLiveTest.testCreateNodeWithSecurityGroup:103
» RunNodes
AzureComputeSecurityGroupExtensionLiveTest>BaseSecurityGroupExtensionLiveTest.testAddIpPermission:135>BaseSecurityGroupExtensionLiveTest.getGroup:457
» NullPointer
AzureComputeSecurityGroupExtensionLiveTest>BaseSecurityGroupExtensionLiveTest.testDeleteSecurityGroup:376>BaseSecurityGroupExtensionLiveTest.getGroup:457
» NullPointer
Tests run: 214, Failures: 9, Errors: 0, Skipped: 10
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:08 h
[INFO] Finished at: 2017-11-28T15:47:12-08:00
[INFO] Final Memory: 50M/377M
[INFO] ------------------------------------------------------------------------
On Tue, Nov 28, 2017 at 10:13 PM, Ignasi Barrera <na...@apache.org> wrote:
> It would be great if you can share the details, Jim. I ran the entire live
> test suite and there was only one failure in the metrics test... I'm
> curious about the failures you've seen.
> Many thanks for taking the time and helping with the release validation!
>
> @demobox, +1 to file an issue to properly track this. Do you know if with
> our current plan we could have some Windows build in CloudBees?
>
>
>
>
> On Nov 29, 2017 4:10 AM, "Jim Spring" <jm...@gmail.com> wrote:
>
> I've seen a mix of azurecompute-arm failures (sorry, I'll enumerate
> tomorrow), but nothing to hold up the release.
>
> Small things like password requirements changing.
>
> -jim
>
> On Tue, Nov 28, 2017 at 5:52 PM, Andrew Phillips <ap...@qrmedia.com>
> wrote:
>>> However, I am unclear on why the test fails since the filesystem
> blobstore
>>> should convert user input /
>>> to backend fs separator \ on Windows. That is to say, code which runs on
>>> Linux and Windows *should*
>>> behave identically, although in previous releases they did not.
>>
>>
>> PR to prevent the test failure here:
>> https://github.com/jclouds/jclouds/pull/1162
>>
>> I'm not sure this change is correct, given that (as Andrew G pointed out)
>> the code is actually *not* expected to fail on Windows (and thus the test
> is
>> expected to pass).
>>
>> From a quick local test, this test was already failing in 2.0.2 (when it
> was
>> first added [1]), so the original implementation may simply have been
>> incomplete. Since we have't seen any related comments or issues, as far
> as I
>> am aware, I'd agree that this is probably not a reason to stop the
> release.
>>
>> Would it make sense to try to fix the underlying problem, or at least
> open a
>> bug to track this, though?
>>
>> Regards
>>
>> ap
>>
>> [1]
>> https://github.com/jclouds/jclouds/commit/6452960c72a5f8247acae12481b94c
> df9d8e4218#diff-9592ea1a2837c5f2cd419db6bde4fd5d
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Andrew Phillips <ap...@qrmedia.com>.
> +1 to file an issue to properly track this.
https://issues.apache.org/jira/browse/JCLOUDS-1361
> Do you know if with our current plan we could have some Windows build
> in CloudBees?
Based on
https://go.cloudbees.com/docs/cloudbees-documentation/dev-at-cloud/#operating-system,
I suspect the answer is "no" :-(
@abayer: any thoughts on that?
Regards
ap
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Ignasi Barrera <na...@apache.org>.
It would be great if you can share the details, Jim. I ran the entire live
test suite and there was only one failure in the metrics test... I'm
curious about the failures you've seen.
Many thanks for taking the time and helping with the release validation!
@demobox, +1 to file an issue to properly track this. Do you know if with
our current plan we could have some Windows build in CloudBees?
On Nov 29, 2017 4:10 AM, "Jim Spring" <jm...@gmail.com> wrote:
I've seen a mix of azurecompute-arm failures (sorry, I'll enumerate
tomorrow), but nothing to hold up the release.
Small things like password requirements changing.
-jim
On Tue, Nov 28, 2017 at 5:52 PM, Andrew Phillips <ap...@qrmedia.com>
wrote:
>> However, I am unclear on why the test fails since the filesystem
blobstore
>> should convert user input /
>> to backend fs separator \ on Windows. That is to say, code which runs on
>> Linux and Windows *should*
>> behave identically, although in previous releases they did not.
>
>
> PR to prevent the test failure here:
> https://github.com/jclouds/jclouds/pull/1162
>
> I'm not sure this change is correct, given that (as Andrew G pointed out)
> the code is actually *not* expected to fail on Windows (and thus the test
is
> expected to pass).
>
> From a quick local test, this test was already failing in 2.0.2 (when it
was
> first added [1]), so the original implementation may simply have been
> incomplete. Since we have't seen any related comments or issues, as far
as I
> am aware, I'd agree that this is probably not a reason to stop the
release.
>
> Would it make sense to try to fix the underlying problem, or at least
open a
> bug to track this, though?
>
> Regards
>
> ap
>
> [1]
> https://github.com/jclouds/jclouds/commit/6452960c72a5f8247acae12481b94c
df9d8e4218#diff-9592ea1a2837c5f2cd419db6bde4fd5d
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Jim Spring <jm...@gmail.com>.
I've seen a mix of azurecompute-arm failures (sorry, I'll enumerate
tomorrow), but nothing to hold up the release.
Small things like password requirements changing.
-jim
On Tue, Nov 28, 2017 at 5:52 PM, Andrew Phillips <ap...@qrmedia.com> wrote:
>> However, I am unclear on why the test fails since the filesystem blobstore
>> should convert user input /
>> to backend fs separator \ on Windows. That is to say, code which runs on
>> Linux and Windows *should*
>> behave identically, although in previous releases they did not.
>
>
> PR to prevent the test failure here:
> https://github.com/jclouds/jclouds/pull/1162
>
> I'm not sure this change is correct, given that (as Andrew G pointed out)
> the code is actually *not* expected to fail on Windows (and thus the test is
> expected to pass).
>
> From a quick local test, this test was already failing in 2.0.2 (when it was
> first added [1]), so the original implementation may simply have been
> incomplete. Since we have't seen any related comments or issues, as far as I
> am aware, I'd agree that this is probably not a reason to stop the release.
>
> Would it make sense to try to fix the underlying problem, or at least open a
> bug to track this, though?
>
> Regards
>
> ap
>
> [1]
> https://github.com/jclouds/jclouds/commit/6452960c72a5f8247acae12481b94cdf9d8e4218#diff-9592ea1a2837c5f2cd419db6bde4fd5d
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Andrew Phillips <ap...@qrmedia.com>.
> However, I am unclear on why the test fails since the filesystem
> blobstore should convert user input /
> to backend fs separator \ on Windows. That is to say, code which runs
> on Linux and Windows *should*
> behave identically, although in previous releases they did not.
PR to prevent the test failure here:
https://github.com/jclouds/jclouds/pull/1162
I'm not sure this change is correct, given that (as Andrew G pointed
out) the code is actually *not* expected to fail on Windows (and thus
the test is expected to pass).
From a quick local test, this test was already failing in 2.0.2 (when it
was first added [1]), so the original implementation may simply have
been incomplete. Since we have't seen any related comments or issues, as
far as I am aware, I'd agree that this is probably not a reason to stop
the release.
Would it make sense to try to fix the underlying problem, or at least
open a bug to track this, though?
Regards
ap
[1]
https://github.com/jclouds/jclouds/commit/6452960c72a5f8247acae12481b94cdf9d8e4218#diff-9592ea1a2837c5f2cd419db6bde4fd5d
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Andrew Gaul <ga...@apache.org>.
We should not block the release for the Windows failure since it only
involves test input and the main changes were trivial, propagating a
different exception type. However, I am unclear on why the test fails
since the filesystem blobstore should convert user input / to backend fs
separator \ on Windows. That is to say, code which runs on Linux and
Windows *should* behave identically, although in previous releases they
did not.
Unfortunately these Windows filesystem issues are common since most
development happens on Linux. JCLOUDS-754 might give us a path forward.
On Mon, Nov 27, 2017 at 02:20:43PM +0100, Ignasi Barrera wrote:
> Andrew, regarding the test, I'd say an input string for each OS would make
> sense. @gaul, WDYT?
> Regarding the release, if this is just about the test configuration but not
> the behavior of the filesystem API itself, I'd say we should not block the
> release for this reason?
>
> @andrea, thanks for running it on Java 7. May you post your vote by
> replying to the [VOTE] thread? It is a PITA that Gmail collapses both
> threads as one. One way to see the threads properly is to temporarily go to
> the Gmail settings, and turn the conversation view off.
> Regarding the failure in Java 8, I think it is some configuration in the
> vagrant-java-bindings library we use. Perhaps @neykov can help here?
>
> *Caused by: org.osgi.framework.BundleException: Unresolved constraint in
> bundle name.neykov.vagrant-java-bindings [87]: Unable to resolve 87.0:
> missing requirement [87.0] osgi.ee <http://osgi.ee>; (&(osgi.ee
> <http://osgi.ee>=JavaSE)(version=1.6))*
>
>
> On 26 November 2017 at 21:35, Andrea Turli <an...@gmail.com> wrote:
>
> > hi,
> >
> > I've just rebuilt with java 7
> >
> > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> > 2017-10-18T07:58:13Z)
> > Maven home: /usr/share/maven
> > Java version: 1.7.0_151, vendor: Oracle Corporation
> > Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> > Default locale: en, platform encoding: UTF-8
> > OS name: "linux", version: "4.9.44-linuxkit-aufs", arch: "amd64", family:
> > "unix"
> >
> > and jclouds-karaf has no issues
> >
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache jclouds :: Karaf ............................ SUCCESS [
> > 46.836 s]
> > [INFO] jclouds :: Karaf :: Core ........................... SUCCESS [
> > 5.985 s]
> > [INFO] jclouds :: Karaf :: Bundles ........................ SUCCESS [
> > 0.172 s]
> > [INFO] jclouds :: Karaf :: JSch Agentproxy for JSch (shaded bundle) SUCCESS
> > [ 5.848 s]
> > [INFO] jclouds :: Karaf :: Utils .......................... SUCCESS [
> > 2.720 s]
> > [INFO] jclouds :: Karaf :: Recipe ......................... SUCCESS [
> > 2.926 s]
> > [INFO] jclouds :: Karaf :: Cache .......................... SUCCESS [
> > 3.302 s]
> > [INFO] jclouds :: Karaf :: Services ....................... SUCCESS [
> > 7.548 s]
> > [INFO] jclouds :: Karaf :: Commands ....................... SUCCESS [
> > 13.752 s]
> > [INFO] jclouds :: Karaf :: URL Handler .................... SUCCESS [
> > 2.393 s]
> > [INFO] jclouds :: Karaf :: Chef ........................... SUCCESS [
> > 0.370 s]
> > [INFO] jclouds :: Karaf :: Chef :: Core ................... SUCCESS [
> > 1.955 s]
> > [INFO] jclouds :: Karaf :: Chef :: Services ............... SUCCESS [
> > 4.195 s]
> > [INFO] jclouds :: Karaf :: Chef :: Commands ............... SUCCESS [
> > 8.073 s]
> > [INFO] jclouds :: Karaf :: Chef :: Cache .................. SUCCESS [
> > 2.842 s]
> > [INFO] jclouds :: Karaf :: Feature ........................ SUCCESS [
> > 7.439 s]
> > [INFO] jclouds :: Karaf :: Integration Tests .............. SUCCESS [17:05
> > min]
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD SUCCESS
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 19:04 min
> > [INFO] Finished at: 2017-11-26T20:28:31Z
> > [INFO] Final Memory: 42M/280M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> >
> > I change my vote to +1
> >
> > On Sun, Nov 26, 2017 at 9:20 PM, Andrew Phillips <ap...@qrmedia.com>
> > wrote:
> >
> > > Please use this thread for discussion of issues uncovered in the RC,
> > >> questions you may have about the RC, etc.
> > >>
> > >
> > > The following test fails repeatedly for me on Windows:
> > >
> > > Failed tests:
> > > FilesystemStorageStrategyImplTest.testDeletingInvalidPathFil
> > > eEndsNormally:695
> > > Deleting an invalid path ended with an InvalidPathException.
> > >
> > > Specifically, it's the "/" character in the test input "A<!:!@#$%^&*?]8
> > > /\0"; removing that works.
> > >
> > > Would having an OS-specific test input seem like the correct solution? Or
> > > should the test be modified to expect a test failure on Windows?
> > >
> > > Regards
> > >
> > > ap
> > >
> >
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Ignasi Barrera <na...@apache.org>.
Andrew, regarding the test, I'd say an input string for each OS would make
sense. @gaul, WDYT?
Regarding the release, if this is just about the test configuration but not
the behavior of the filesystem API itself, I'd say we should not block the
release for this reason?
@andrea, thanks for running it on Java 7. May you post your vote by
replying to the [VOTE] thread? It is a PITA that Gmail collapses both
threads as one. One way to see the threads properly is to temporarily go to
the Gmail settings, and turn the conversation view off.
Regarding the failure in Java 8, I think it is some configuration in the
vagrant-java-bindings library we use. Perhaps @neykov can help here?
*Caused by: org.osgi.framework.BundleException: Unresolved constraint in
bundle name.neykov.vagrant-java-bindings [87]: Unable to resolve 87.0:
missing requirement [87.0] osgi.ee <http://osgi.ee>; (&(osgi.ee
<http://osgi.ee>=JavaSE)(version=1.6))*
On 26 November 2017 at 21:35, Andrea Turli <an...@gmail.com> wrote:
> hi,
>
> I've just rebuilt with java 7
>
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T07:58:13Z)
> Maven home: /usr/share/maven
> Java version: 1.7.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "4.9.44-linuxkit-aufs", arch: "amd64", family:
> "unix"
>
> and jclouds-karaf has no issues
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache jclouds :: Karaf ............................ SUCCESS [
> 46.836 s]
> [INFO] jclouds :: Karaf :: Core ........................... SUCCESS [
> 5.985 s]
> [INFO] jclouds :: Karaf :: Bundles ........................ SUCCESS [
> 0.172 s]
> [INFO] jclouds :: Karaf :: JSch Agentproxy for JSch (shaded bundle) SUCCESS
> [ 5.848 s]
> [INFO] jclouds :: Karaf :: Utils .......................... SUCCESS [
> 2.720 s]
> [INFO] jclouds :: Karaf :: Recipe ......................... SUCCESS [
> 2.926 s]
> [INFO] jclouds :: Karaf :: Cache .......................... SUCCESS [
> 3.302 s]
> [INFO] jclouds :: Karaf :: Services ....................... SUCCESS [
> 7.548 s]
> [INFO] jclouds :: Karaf :: Commands ....................... SUCCESS [
> 13.752 s]
> [INFO] jclouds :: Karaf :: URL Handler .................... SUCCESS [
> 2.393 s]
> [INFO] jclouds :: Karaf :: Chef ........................... SUCCESS [
> 0.370 s]
> [INFO] jclouds :: Karaf :: Chef :: Core ................... SUCCESS [
> 1.955 s]
> [INFO] jclouds :: Karaf :: Chef :: Services ............... SUCCESS [
> 4.195 s]
> [INFO] jclouds :: Karaf :: Chef :: Commands ............... SUCCESS [
> 8.073 s]
> [INFO] jclouds :: Karaf :: Chef :: Cache .................. SUCCESS [
> 2.842 s]
> [INFO] jclouds :: Karaf :: Feature ........................ SUCCESS [
> 7.439 s]
> [INFO] jclouds :: Karaf :: Integration Tests .............. SUCCESS [17:05
> min]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 19:04 min
> [INFO] Finished at: 2017-11-26T20:28:31Z
> [INFO] Final Memory: 42M/280M
> [INFO]
> ------------------------------------------------------------------------
>
>
> I change my vote to +1
>
> On Sun, Nov 26, 2017 at 9:20 PM, Andrew Phillips <ap...@qrmedia.com>
> wrote:
>
> > Please use this thread for discussion of issues uncovered in the RC,
> >> questions you may have about the RC, etc.
> >>
> >
> > The following test fails repeatedly for me on Windows:
> >
> > Failed tests:
> > FilesystemStorageStrategyImplTest.testDeletingInvalidPathFil
> > eEndsNormally:695
> > Deleting an invalid path ended with an InvalidPathException.
> >
> > Specifically, it's the "/" character in the test input "A<!:!@#$%^&*?]8
> > /\0"; removing that works.
> >
> > Would having an OS-specific test input seem like the correct solution? Or
> > should the test be modified to expect a test failure on Windows?
> >
> > Regards
> >
> > ap
> >
>
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Andrea Turli <an...@gmail.com>.
hi,
I've just rebuilt with java 7
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T07:58:13Z)
Maven home: /usr/share/maven
Java version: 1.7.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "4.9.44-linuxkit-aufs", arch: "amd64", family:
"unix"
and jclouds-karaf has no issues
[INFO] Reactor Summary:
[INFO]
[INFO] Apache jclouds :: Karaf ............................ SUCCESS [
46.836 s]
[INFO] jclouds :: Karaf :: Core ........................... SUCCESS [
5.985 s]
[INFO] jclouds :: Karaf :: Bundles ........................ SUCCESS [
0.172 s]
[INFO] jclouds :: Karaf :: JSch Agentproxy for JSch (shaded bundle) SUCCESS
[ 5.848 s]
[INFO] jclouds :: Karaf :: Utils .......................... SUCCESS [
2.720 s]
[INFO] jclouds :: Karaf :: Recipe ......................... SUCCESS [
2.926 s]
[INFO] jclouds :: Karaf :: Cache .......................... SUCCESS [
3.302 s]
[INFO] jclouds :: Karaf :: Services ....................... SUCCESS [
7.548 s]
[INFO] jclouds :: Karaf :: Commands ....................... SUCCESS [
13.752 s]
[INFO] jclouds :: Karaf :: URL Handler .................... SUCCESS [
2.393 s]
[INFO] jclouds :: Karaf :: Chef ........................... SUCCESS [
0.370 s]
[INFO] jclouds :: Karaf :: Chef :: Core ................... SUCCESS [
1.955 s]
[INFO] jclouds :: Karaf :: Chef :: Services ............... SUCCESS [
4.195 s]
[INFO] jclouds :: Karaf :: Chef :: Commands ............... SUCCESS [
8.073 s]
[INFO] jclouds :: Karaf :: Chef :: Cache .................. SUCCESS [
2.842 s]
[INFO] jclouds :: Karaf :: Feature ........................ SUCCESS [
7.439 s]
[INFO] jclouds :: Karaf :: Integration Tests .............. SUCCESS [17:05
min]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19:04 min
[INFO] Finished at: 2017-11-26T20:28:31Z
[INFO] Final Memory: 42M/280M
[INFO]
------------------------------------------------------------------------
I change my vote to +1
On Sun, Nov 26, 2017 at 9:20 PM, Andrew Phillips <ap...@qrmedia.com>
wrote:
> Please use this thread for discussion of issues uncovered in the RC,
>> questions you may have about the RC, etc.
>>
>
> The following test fails repeatedly for me on Windows:
>
> Failed tests:
> FilesystemStorageStrategyImplTest.testDeletingInvalidPathFil
> eEndsNormally:695
> Deleting an invalid path ended with an InvalidPathException.
>
> Specifically, it's the "/" character in the test input "A<!:!@#$%^&*?]8
> /\0"; removing that works.
>
> Would having an OS-specific test input seem like the correct solution? Or
> should the test be modified to expect a test failure on Windows?
>
> Regards
>
> ap
>
Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1
Posted by Andrew Phillips <ap...@qrmedia.com>.
> Please use this thread for discussion of issues uncovered in the RC,
> questions you may have about the RC, etc.
The following test fails repeatedly for me on Windows:
Failed tests:
FilesystemStorageStrategyImplTest.testDeletingInvalidPathFileEndsNormally:695
Deleting an invalid path ended with an InvalidPathException.
Specifically, it's the "/" character in the test input "A<!:!@#$%^&*?]8
/\0"; removing that works.
Would having an OS-specific test input seem like the correct solution?
Or should the test be modified to expect a test failure on Windows?
Regards
ap