You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am trying to run flacoco to generate the fault localisation for apache-camel
When running in verbose mode it gives me the following error. The weird thing is that on smaller projects everything seems to work. The project has been built and tests ran. Then used maven to genearte the classpath.info and pass it as per tutorial to flacoco.
Also the timeout has been set to the largest integer and the following results was received.
The text was updated successfully, but these errors were encountered:
I tried to reproduce this by running flacoco on camel-core (I assumed, by the path, that this is the module you are trying to execute. Let me know if I made a wrong assumption).
First, my execution successfully terminated, so I don't know why you are getting that NullPointerException.
Maybe you could provide me with more details to correctly reproduce that error such as the commitId you are trying to execute, and the complete command.
Second, the WARN TestMethodFilter - NoClassDefFoundError is related to the test detection phase. This warning is reported when our test detection mechanism, which is based on a classloader, tries to load a class which is not provided in the classpath. This may indicate an error in the classpath definition, for instance, not allowing flacoco to access the classes it is trying to load.
Lastly, I did not understand what you meant by "but verbose mode are correct". Could you further elaborate on that?
Hi, I am trying to run flacoco to generate the fault localisation for apache-camel
When running in verbose mode it gives me the following error. The weird thing is that on smaller projects everything seems to work. The project has been built and tests ran. Then used maven to genearte the classpath.info and pass it as per tutorial to flacoco.
Also the timeout has been set to the largest integer and the following results was received.
The text was updated successfully, but these errors were encountered: