search

STAMP-project / EvoCrash-demo

See https://stamp-project.github.io/botsing/ for the latest version of STAMP crash reproduction tool.
https://stamp-project.github.io/botsing/
Apache License 2.0
1 stars 2 forks source link

To ease readability/debugging #13

Closed mbenguig closed 6 years ago

mbenguig commented 6 years ago

Improvements:

The first difficulties we encountered were related to malformed log files. Indeed, exceptions do not clearly expose the reason.

Target exception was set to: com.fasterxml.jackson.core.JsonParseException LogParser: Failed to parse the log file!

In a perfect world, user would directly analyze log files without pre processing.

The test generation execution trace requires more meaningful messages, to clearly distinguish ML related steps. Moreover, some logs are not required for a default utilization and could be enabled at a higher log level. This latter could be set from a dedicated property file. The notion of budget was not clear until i found its definition on the evosuite website.

pderakhshanfar commented 6 years ago

In EvoCrash case, the log file is the stack trace. This exception happens when the stack trace directory did not set right. About the properties, I sent you a link for understanding properties better. I will send it here again. Each of the properties has a description in front of it.

https://github.com/EvoSuite/evosuite/blob/master/client/src/main/java/org/evosuite/Properties.java

PascalUrso commented 6 years ago

Sure, but the error "Target exception was set to: com.fasterxml.jackson.core.JsonParseException LogParser: Failed to parse the log file!" could be more informative / user friendly

pderakhshanfar commented 6 years ago

Yes, I agree with you that we should improve the informativity of the output. We will take care of that after completing our studies about crash replication with EvoCrash. There are lots of paths that we can work on them for improving the rate of crash replication.

xdevroey commented 6 years ago

The exception is thrown by the LogParser class. EvoCrash being a research tool, the user feedback is indeed sometimes limited, sorry. If you have some time, please do not hesitate to contribute here, it will be much appreciated :-)

In the meantime, if you send us a copy of the log file (or put it here in an answer), we should be able to tell you what goes wrong.

xdevroey commented 6 years ago

See https://github.com/STAMP-project/EvoCrash/issues/5 and https://github.com/STAMP-project/EvoCrash/issues/6