-
Notifications
You must be signed in to change notification settings - Fork 75
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
VerifyError: Inconsistent stackmap frames #147
Comments
Thanks for reporting this. However, I can't reproduce it. I've downloaded Android Studio 2.1.2, but I still get a green bar without error when I run a test that uses EV with coverage. Can you provide me a small but complete project that reproduces this issue? |
Here it is: https://github.com/koral--/equalsverifiertest |
Thanks, I was able to reproduce the issue with this project. I'll let you know when I know more :). |
It probably has to do with the fact that EqualsVerifier compiles for Java 7, but it does interact with classes of the Java 8 APIs if they're available (in this case, it failed on JavaFX's ObservableList). I have a fix, and I'll make a release tonight. |
Released in version 2.1.1! |
What steps will reproduce the problem?
Execute test using EqualsVerifier with Intellij code coverage on OSX.
What is the code that triggers this problem?
All usages of
EqualsVerifier.forClass()
are failing. Eg:What error message or stack trace does EqualsVerifier give?
What did you expect?
There should be no failure. The same test works in all other known configurations executions eg. in Android Studio without code coverage, from commadline (without IDE), on the same JDK version on Linux.
Which version of EqualsVerifier are you using?
2.1
Please provide any additional information below.
The latest Oracle JDK 8:
The latest stable Android Studio:
Android Studio 2.1.2 Build#AI-143.2915827
I'm not sure if bug is located in EqualsVerifier, but according to this SO post it may be, so I'm first reporting it here. Indeed adding
-noverify
JVM argument works.The text was updated successfully, but these errors were encountered: