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

No proper info/warning when mismatch of version between Core and Driver processes #793

Open
italktothewind opened this issue Aug 24, 2023 · 4 comments

Comments

@italktothewind
Copy link

Hi, I'm having the following error when EvoMaster tries to call the driver:

* EvoMaster version: 1.6.2-SNAPSHOT
* Initializing...
02:41:25.343 [main] ERROR o.e.c.r.service.RemoteController - Driver error. HTTP status 400. Error: Unrecognized field "resetCustomizedMethodForMockObject" (class org.evomaster.client.java.controller.api.dto.SutRunDto), not marked as ignorable (6 known properties: "calculateSqlHeuristics", "resetState", "resetMockedExternalServicesWithCustomizedMethod", "run", "methodReplacementCategories", "extractSqlExecutionInfo"])
 at [Source: (shaded.org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 73] (through reference chain: org.evomaster.client.java.controller.api.dto.SutRunDto["resetCustomizedMethodForMockObject"])
02:41:25.344 [main] WARN  o.e.c.r.service.RemoteController - Failed to change running state of the SUT. HTTP status 400. Error: 'null
* [ERROR] ERROR related to the system under test: Failed to start the SUT
  For white-box testing, look at the logs of the EvoMaster Driver to help debugging this problem.

Steps to reproduce it:

  1. Run src/main/java/em/embedded/org/javiermf/features/EmbeddedEvoMasterController.java from the latest version of EMB
  2. Run src/main/kotlin/org/evomaster/core/Main.kt from the latest version of EvoMaster
  3. I got that error on EvoMaster. No errors reported in the driver (at DEBUG level). Same error occurs in EvoMaster if instead of step 2) I generate core/target/evomaster.jar and then I run that jar using java -jar.

In both IDE (IDEA) projects I'm using Java 8 as SDK

Any advice?

Thanks!

@italktothewind
Copy link
Author

The issue was that EMB was using 1.6.1 version of EvoMaster and my version of EvoMaster was 1.6.2-SNAPSHOT and SutRunDto has different fields in each versions.

@arcuri82
Copy link
Collaborator

hi,

when you tried with core/target/evomaster.jar, wasn't there a warning stating the versions are different? (such warning is not there when running directly from IDE)

@italktothewind
Copy link
Author

italktothewind commented Aug 24, 2023

Hi,

I don't see a warning, this is the full log when I tried with the jar:

 _____          ___  ___          _
|  ___|         |  \/  |         | |
| |____   _____ | .  . | __ _ ___| |_ ___ _ __
|  __\ \ / / _ \| |\/| |/ _` / __| __/ _ \ '__|
| |___\ V / (_) | |  | | (_| \__ \ ||  __/ |
\____/ \_/ \___/\_|  |_/\__,_|___/\__\___|_|

                    
* EvoMaster version: 1.6.2-SNAPSHOT
* Initializing...
04:34:54.651 [main] ERROR o.e.c.r.service.RemoteController - Driver error. HTTP status 400. Error: Unrecognized field "resetCustomizedMethodForMockObject" (class org.evomaster.client.java.controller.api.dto.SutRunDto), not marked as ignorable (6 known properties: "calculateSqlHeuristics", "resetState", "resetMockedExternalServicesWithCustomizedMethod", "run", "methodReplacementCategories", "extractSqlExecutionInfo"])
 at [Source: (shaded.org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 73] (through reference chain: org.evomaster.client.java.controller.api.dto.SutRunDto["resetCustomizedMethodForMockObject"])
04:34:54.652 [main] WARN  o.e.c.r.service.RemoteController - Failed to change running state of the SUT. HTTP status 400. Error: 'null
* [ERROR] ERROR related to the system under test: Failed to start the SUT
  For white-box testing, look at the logs of the EvoMaster Driver to help debugging this problem.

@arcuri82 arcuri82 reopened this Aug 24, 2023
@arcuri82 arcuri82 added the bug label Aug 24, 2023
@arcuri82
Copy link
Collaborator

arcuri82 commented Aug 24, 2023

hi,
thanks. then this is a bug, because there should be a clear warning there, and possibly better error message

@arcuri82 arcuri82 changed the title Driver is returning 400 when called No proper info/warning when mismatch of version between Core and Driver processes Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants