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.

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

KPIs are not really informative now #2032

Open
yegor256 opened this issue May 9, 2019 · 13 comments
Open

KPIs are not really informative now #2032

yegor256 opened this issue May 9, 2019 · 13 comments
Labels
kpi KPI metrics scope

Comments

@yegor256
Copy link
Member

yegor256 commented May 9, 2019

Let's make them look better and more informative.

@0crat
Copy link
Collaborator

0crat commented May 9, 2019

@g4s8/z please, pay attention to this issue

@yegor256
Copy link
Member Author

yegor256 commented May 9, 2019

@g4s8 I will do it, in a few PRs

@yegor256 yegor256 self-assigned this May 9, 2019
yegor256 added a commit that referenced this issue May 9, 2019
@0crat 0crat added the scope label May 9, 2019
@0crat
Copy link
Collaborator

0crat commented May 9, 2019

The job #2032 assigned to @yegor256/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented May 9, 2019

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @yegor256/z

@0crat
Copy link
Collaborator

0crat commented May 9, 2019

Bug was reported, see §29: +15 point(s) just awarded to @yegor256/z

@0crat
Copy link
Collaborator

0crat commented May 9, 2019

It is strongly discouraged to assign jobs to their creators, see §19: -15 point(s) just awarded to @yegor256/z

@g4s8
Copy link
Collaborator

g4s8 commented May 11, 2019

@rultor release, tag=0.46.11

@rultor
Copy link
Contributor

rultor commented May 11, 2019

@rultor release, tag=0.46.11

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

@rultor
Copy link
Contributor

rultor commented May 11, 2019

@rultor release, tag=0.46.11

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

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.774 sec - in com.zerocracy.radars.github.RbAddToMilestoneTest
Running com.zerocracy.tk.TkBoardTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0 sec - in com.zerocracy.tk.TkBoardTest
Running com.zerocracy.pmo.PeopleTest
Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.251 sec - in com.zerocracy.pmo.PeopleTest
Running com.zerocracy.tools.SignatureTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec - in com.zerocracy.tools.SignatureTest

Results :

Tests in error: 
  SyncFarmTest.makesProjectsThreadSafe:67 » TestTimedOut test timed out after 5 ...

Tests run: 575, Failures: 0, Errors: 1, Skipped: 17

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project farm: There are test failures.
[ERROR] 
[ERROR] Please refer to /home/r/repo/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project farm: There are test failures.

Please refer to /home/r/repo/target/surefire-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:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	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/surefire-reports for the individual test results.
	at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:91)
	at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:320)
	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:892)
	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:755)
	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 1df805e38f2f1715c719bf86cd3c3679d7c610c6e360e2a918ead82aafd8740c is dead
Sat May 11 12:29:16 CEST 2019

@g4s8
Copy link
Collaborator

g4s8 commented May 11, 2019

@rultor release, tag=0.46.11

@rultor
Copy link
Contributor

rultor commented May 11, 2019

@rultor release, tag=0.46.11

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

@rultor
Copy link
Contributor

rultor commented May 11, 2019

@rultor release, tag=0.46.11

@g4s8 Done! FYI, the full log is here (took me 17min)

@g4s8 g4s8 added the kpi KPI metrics label May 18, 2019
@yegor256 yegor256 removed their assignment Sep 10, 2022
@0crat
Copy link
Collaborator

0crat commented Sep 10, 2022

@yegor256/z I see that you unassigned this issue; the order is still assigned to @yegor256/z though; to cancel the order use refuse, as in §6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kpi KPI metrics scope
Projects
None yet
Development

No branches or pull requests

4 participants