-
Notifications
You must be signed in to change notification settings - Fork 306
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
Code coverage analysis does not support Jsoup-{4,6,9} #627
Comments
Hi,
I faced similar issues while collecting coverage for Jsoup using GZoltar. Moreover, while collecting test coverage using GZoltar for JacksonDatabind {58-63}, {65, 66, 67, 68, 69, 70,71, 72, 73}, {75, 76, 77, 78, 79}, using the relevant test, a ClassCircularityError was thrown. I ran GZoltar till version 79. For JacksonDatabind defects ({1-57}, 64, 74), code coverage ran. I have added the stacktrace below while collecting coverage for bug-58. (Similar error for all the mentioned version if a relevant test uses AccessFixTest class>> AccessFixTest$CauseBlockingSecurityManager.checkPermission) java.util.concurrent.ExecutionException: java.lang.ClassCircularityError: java/security/Permission |
For Jsoup. GZoltar failed to run coverage for bug {1-53}, however {54-93}, I could collect coverage data. |
@JoyKrishan Just to clarify: You are observing GZoltar failing on additional Jsoup and JacksonDatabind defects, but you are not observing |
@rjust Yes, correct. |
@jose Is this something that should be tracked on the GZoltar side? |
Hi @jose, For your reference, Defects4J V2.1.0
|
Code coverage does not run on three Jsoup defects (4, 6, and 9) -- the code coverage instrumentation exceeds the method size bytecode limit for these defects.
The text was updated successfully, but these errors were encountered: