Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FkRegion/FkBucket with default temp dir #54

Closed
yegor256 opened this issue Sep 5, 2017 · 13 comments
Closed

FkRegion/FkBucket with default temp dir #54

yegor256 opened this issue Sep 5, 2017 · 13 comments
Assignees
@yegor256

Comments

@yegor256
Copy link
Member

yegor256 commented Sep 5, 2017

Let's make it default
@yegor256 yegor256 self-assigned this Sep 5, 2017
@0crat
Copy link

0crat commented Sep 5, 2017

Job gh:jcabi/jcabi-s3#54 assigned to @yegor256, please go ahead (policy).

@0crat
Copy link

0crat commented Sep 5, 2017

+15 points just awarded to @yegor256, total is +2970.

yegor256 added a commit that referenced this issue Sep 5, 2017
@yegor256
#54 more ctors
eaa8735
yegor256 added a commit that referenced this issue Sep 5, 2017
@yegor256
#54 parent up
59356ce
yegor256 added a commit that referenced this issue Sep 5, 2017
@yegor256
#54 aws version up
32fd4b5
@yegor256
Copy link
Member Author

yegor256 commented Sep 5, 2017

@rultor release, tag is 0.17

@rultor
Copy link
Contributor

rultor commented Sep 5, 2017

@rultor release, tag is 0.17

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented Sep 5, 2017

@rultor release, tag is 0.17

@yegor256 Oops, I failed. You can see the full log here (spent 11min)

  AwsOcketITCase.readsAndWritesObjectContent ? SdkClient Unable to find a region...
  AwsOcketITCase.throwsWhenObjectIsAbsent ? SdkClient Unable to find a region vi...
  RegionITCase.connectsToAmazon ? SdkClient Unable to find a region via the regi...

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

[INFO] 
[INFO] --- maven-failsafe-plugin:2.19.1:verify (default) @ jcabi-s3 ---
[INFO] Failsafe report directory: /home/r/repo/target/failsafe-reports
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:23 min
[INFO] Finished at: 2017-09-05T12:57:59+00:00
[INFO] Final Memory: 64M/540M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (default) on project jcabi-s3: There are test failures.
[ERROR] 
[ERROR] Please refer to /home/r/repo/target/failsafe-reports for the individual test results.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (default) on project jcabi-s3: There are test failures.

Please refer to /home/r/repo/target/failsafe-reports for the individual test results.
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.

Please refer to /home/r/repo/target/failsafe-reports for the individual test results.
	at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:91)
	at org.apache.maven.plugin.failsafe.VerifyMojo.execute(VerifyMojo.java:202)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
	... 20 more
[ERROR] 
[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
container c19a6ad13b0c56222f34e5fe8b9bee288b7da827bc20ff29482ccb3db3608e5b is dead
Tue Sep  5 14:58:50 CEST 2017

yegor256 added a commit that referenced this issue Sep 5, 2017
@yegor256
#54 region
0aeb0e4
@yegor256
Copy link
Member Author

yegor256 commented Sep 5, 2017

@rultor release, tag is 0.17

@rultor
Copy link
Contributor

rultor commented Sep 5, 2017

@rultor release, tag is 0.17

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented Sep 5, 2017

@rultor release, tag is 0.17

@yegor256 Oops, I failed. You can see the full log here (spent 11min)


Tests in error: 
  AwsBucketITCase.existsNonExistingBucket ? AmazonS3 The specified bucket does n...

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

[INFO] 
[INFO] --- maven-failsafe-plugin:2.19.1:verify (default) @ jcabi-s3 ---
[INFO] Failsafe report directory: /home/r/repo/target/failsafe-reports
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:08 min
[INFO] Finished at: 2017-09-05T13:17:31+00:00
[INFO] Final Memory: 68M/491M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (default) on project jcabi-s3: There are test failures.
[ERROR] 
[ERROR] Please refer to /home/r/repo/target/failsafe-reports for the individual test results.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (default) on project jcabi-s3: There are test failures.

Please refer to /home/r/repo/target/failsafe-reports for the individual test results.
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.

Please refer to /home/r/repo/target/failsafe-reports for the individual test results.
	at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:91)
	at org.apache.maven.plugin.failsafe.VerifyMojo.execute(VerifyMojo.java:202)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
	... 20 more
[ERROR] 
[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
container 12880e81055efd58330a08e1279c7e5630600bef1b718e2b808189a9598f8d49 is dead
Tue Sep  5 15:17:56 CEST 2017

@yegor256
Copy link
Member Author

yegor256 commented Sep 5, 2017

@rultor release, tag is 0.17

@rultor
Copy link
Contributor

rultor commented Sep 5, 2017

@rultor release, tag is 0.17

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented Sep 5, 2017

@rultor release, tag is 0.17

@yegor256 Done! FYI, the full log is here (took me 30min)

@yegor256 yegor256 closed this as completed Sep 5, 2017
@0crat
Copy link

0crat commented Sep 5, 2017

Job gh:jcabi/jcabi-s3#54 is now out of scope.

@0crat
Copy link

0crat commented Sep 5, 2017

+30 points just awarded to @yegor256, total is +3030.

yegor256 added a commit that referenced this issue Sep 5, 2017
@yegor256
#54 extra checks
cdd7216
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yegor256 yegor256

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yegor256 @rultor @0crat