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

new method contains() in Objectionary and OyFake #1567

Merged
merged 25 commits into from
Dec 26, 2022

Conversation

MikhailLipanin
Copy link
Member

@MikhailLipanin MikhailLipanin commented Dec 15, 2022

related #1395

UPD:

  • Moved test classes to their packages

@MikhailLipanin
Copy link
Member Author

@volodya-lombrozo Can you pls have a look?

Copy link
Member

@volodya-lombrozo volodya-lombrozo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MikhailLipanin I'm not sure that it's the best solution to add contains method for Objectionary. Is it the only way to check existence? Do we even need to check it?

@MikhailLipanin
Copy link
Member Author

MikhailLipanin commented Dec 15, 2022

@MikhailLipanin I'm not sure that it's the best solution to add contains method for Objectionary. Is it the only way to check existence? Do we even need to check it?

@volodya-lombrozo It will be used in ProbeMojo, which will check the existence of an object in Objectionary.
The second way to do this is by using get() method and catching an Exception if not found, but it is bad

@MikhailLipanin
Copy link
Member Author

@volodya-lombrozo Can you pls see again?

@MikhailLipanin
Copy link
Member Author

MikhailLipanin commented Dec 21, 2022

@volodya-lombrozo, Note, that here in last commits, I haven't changed anything, except the "style" of code. Not a "logic".
But here is an error, that I mentioned in #1574 ---- this one with error in ParseMojo in Optional

@MikhailLipanin MikhailLipanin changed the title new method contains() in Objectionary and OyLambda new method contains() in Objectionary and OyFake Dec 21, 2022
@MikhailLipanin
Copy link
Member Author

@volodya-lombrozo I think, working github-actions now is a full Random. (see my last 2 commits)

Copy link
Member

@volodya-lombrozo volodya-lombrozo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MikhailLipanin Looks good to me.
@yegor256 Can you merge please?

@MikhailLipanin
Copy link
Member Author

@yegor256, can you merge pls?

@yegor256
Copy link
Member

@rultor merge

@rultor
Copy link
Contributor

rultor commented Dec 25, 2022

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Contributor

rultor commented Dec 25, 2022

@rultor merge

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

    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Coverage checks have not been met. See log for details.
    at org.jacoco.maven.CheckMojo.executeCheck (CheckMojo.java:194)
    at org.jacoco.maven.CheckMojo.executeMojo (CheckMojo.java:169)
    at org.jacoco.maven.AbstractJacocoMojo.execute (AbstractJacocoMojo.java:46)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[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/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :eo-runtime
\u001b[0m\u001b[0mcontainer ba4e71ce8fa68f1f0342e6839588c4fba2a1098b3fbbd32991ab8d5710a40f85 is dead
Sun 25 Dec 2022 06:03:02 AM CET

@MikhailLipanin
Copy link
Member Author

@yegor256, It says that the problem is in eo-runtime, but I haven't changed it in this PR.
Now I have just set COVEREDRATIO values in eo-runtime/pom.xml and checks passed. Is this a valid solution? (Idk, can we change these values)

@volodya-lombrozo
Copy link
Member

@MikhailLipanin It means that your code have not enough tests. In other words, code coverage become less with your PR.
In order to fix that - please, provide more tests in order to increase the code coverage.

@volodya-lombrozo
Copy link
Member

@MikhailLipanin #1614

@MikhailLipanin
Copy link
Member Author

@yegor256 Can you try to merge again pls?

@yegor256
Copy link
Member

@rultor merge

@rultor
Copy link
Contributor

rultor commented Dec 26, 2022

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@0pdd
Copy link

0pdd commented Dec 26, 2022

@MikhailLipanin 2 puzzles #1622, #1623 are still not solved.

@rultor
Copy link
Contributor

rultor commented Dec 26, 2022

@rultor merge

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

@0pdd
Copy link

0pdd commented Dec 28, 2022

@MikhailLipanin the puzzle #1623 is still not solved; solved: #1622.

@0pdd
Copy link

0pdd commented Dec 28, 2022

@MikhailLipanin all 2 puzzles are solved here: #1622, #1623.

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

Successfully merging this pull request may close these issues.

None yet

5 participants