I attached 1.9.x integration test results from atmos, aws-s3, azureblob,
filesystem, google-cloud-storage, and rackspace-cloudfiles-us.  aws-s3
and rackspace-cloudfiles-us required several runs to avoid some
eventually consistent behavior.  google-cloud-storage has three
legitimate failures with the only serious one tracked by JCLOUDS-912.

On Wed, Jul 08, 2015 at 11:31:25PM +0200, Ignasi Barrera wrote:
> Hi!
> 
> Everything is in place to release 1.9.1, but I'd like to propose a
> different approach this time. Usually we run the live tests against
> each RC, but that means cutting new RCs to fix the important live
> tests that fail, which is not an optimal procedure.
> 
> I'd like to propose a "pre-release" period (a week?) to run the live
> tests and fix them so we can have a smooth and great 1.9,1 release. It
> would be great if we could coordinate some provider testing, as not
> everyone knows the details of every provider (and not everyone has an
> account in each one).
> 
> Thinking about the most active contributors, it would be ideal if we
> could split the work like:
> 
> @nacx: aws-ec2, digitalocean and chef.
> @abayer: Could you help with aws-ec2?
> @danbroudy: google-compute-engine, google-cloud-storage.
> @andreaturli: softlayer, docker.
> @zack: rackspace-cloudservers, rackspace-cloudfiles.
> @devjcsrj: can you give some love to ProfitBricks?
> @ilgrosso: could you rune the live tests on Azure Compute?
> @ccustine: would you be able to run the HPCloud Compute live tests?
> @gaul: blobmaster! :)
> 
> @all-mailing-list-subscribers: Any live test feedback on any provider
> is very welcome, and PRs are very welcome too!
> 
> Please, don't misunderstand this as an assignment of tasks! I'm just
> thinking out loud about a way to coordinate work so we can test and
> fix as many broken windows as we can, without duplicating efforts and
> without converting it in a tedious task. Running and fixing live tests
> (there shouldn't be many live tests failing) shouldn't be a tough
> effort, and the benefits for the project are huge.
> 
> 
> If there is an agreement, I'd propose a week of live test run&fix and
> cut the 1.9.1 release on July 15-20. Does this sound like a good plan?
> 
> 
> I.

-- 
Andrew Gaul
http://gaul.org/
$ mvn integration-test -pl :atmos -Plive,atmos

Tests run: 59, Failures: 0, Errors: 0, Skipped: 10

--------------------------------------------------------------------------------

$ mvn integration-test -pl :aws-s3 -Plive,aws-s3

Tests run: 119, Failures: 0, Errors: 0, Skipped: 2

--------------------------------------------------------------------------------

$ mvn integration-test -pl :azureblob -Plive,azureblob

Tests run: 100, Failures: 0, Errors: 0, Skipped: 9

--------------------------------------------------------------------------------

$ mvn integration-test -pl :filesystem

Tests run: 70, Failures: 0, Errors: 0, Skipped: 4

--------------------------------------------------------------------------------

$ mvn integration-test -pl google-cloud-storage -Plive,google-cloud-storage

Failed tests:
  
GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testGetIfMatch:326
 » IllegalState
  
GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutInputStream:566->BaseBlobIntegrationTest.testPut:622
 » HttpResponse
  
GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListContainer:471
 expected [15] but found [14]

Tests run: 117, Failures: 3, Errors: 0, Skipped: 6

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (integration) on 
project google-cloud-storage: There are test failures.
[ERROR]
[ERROR] Please refer to 
/home/gaul/work/jclouds-labs-google/google-cloud-storage/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

--------------------------------------------------------------------------------

$ mvn integration-test -pl :rackspace-cloudfiles-us 
-Plive,rackspace-cloudfiles-us

Tests run: 75, Failures: 0, Errors: 0, Skipped: 11

Reply via email to