Process completed with exit code 1.

Strict stubbing argument mismatch. Please check: - this invocation of 'resolveType' method: classUnderTest.resolveType("NonNull"); -> at org.moreunit.mock.dependencies.Dependencies.resolveTypeSignature(Dependencies.java:133) - has following stubbing(s) with different arguments: 1. classUnderTest.resolveType("ReadOnly"); -> at org.moreunit.mock.dependencies.DependenciesTest.resolveTypeParameters_should_handle_type_annotations(DependenciesTest.java:144) Typically, stubbing argument mismatch indicates user mistake when writing tests. Mockito fails early so that you can debug potential problem easily. However, there are legit scenarios when this exception generates false negative signal: - stubbing the same method multiple times using 'given().will()' or 'when().then()' API Please use 'will().given()' or 'doReturn().when()' API for stubbing. - stubbed method is intentionally invoked with different arguments by code under test Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT). For more information see javadoc for PotentialStubbingProblem class.

Strict stubbing argument mismatch. Please check: - this invocation of 'resolveType' method: classUnderTest.resolveType(""); -> at org.moreunit.mock.dependencies.Dependencies.resolveTypeSignature(Dependencies.java:133) - has following stubbing(s) with different arguments: 1. classUnderTest.resolveType("Set"); -> at org.moreunit.mock.dependencies.DependenciesTest.resolveTypeParameters_should_handle_wildcards(DependenciesTest.java:131) 2. classUnderTest.resolveType("String"); -> at org.moreunit.mock.dependencies.DependenciesTest.resolveTypeParameters_should_handle_wildcards(DependenciesTest.java:132) Typically, stubbing argument mismatch indicates user mistake when writing tests. Mockito fails early so that you can debug potential problem easily. However, there are legit scenarios when this exception generates false negative signal: - stubbing the same method multiple times using 'given().will()' or 'when().then()' API Please use 'will().given()' or 'doReturn().when()' API for stubbing. - stubbed method is intentionally invoked with different arguments by code under test Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT). For more information see javadoc for PotentialStubbingProblem class.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/