Fixed
Status Update
Comments
ag...@google.com <ag...@google.com> #2
I am also on Catalina if it helps.
ag...@google.com <ag...@google.com> #3
I'm also affected but I'm on Windows10. can confirm it on version 4.0 Canary 9
ac...@google.com <ac...@google.com> #4
Happening on junit tests for me as well.
Android Studio 3.6 RC 1
Build #AI-192.7142.36.36.6071332, built on December 13, 2019
Runtime version: 1.8.0_212-release-1586-b4-5784211 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.15.2
GC: ParNew, ConcurrentMarkSweep
Memory: 1237M
Cores: 16
Registry: ide.new.welcome.screen.force=true, ide.tooltip.initialDelay=600
Non-Bundled Plugins: IdeaVIM, org.jetbrains.kotlin, com.squareup.sqldelight
Android Studio 3.6 RC 1
Build #AI-192.7142.36.36.6071332, built on December 13, 2019
Runtime version: 1.8.0_212-release-1586-b4-5784211 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.15.2
GC: ParNew, ConcurrentMarkSweep
Memory: 1237M
Cores: 16
Registry: ide.new.welcome.screen.force=true, ide.tooltip.initialDelay=600
Non-Bundled Plugins: IdeaVIM, org.jetbrains.kotlin, com.squareup.sqldelight
ag...@google.com <ag...@google.com> #5
I'm not yet able to repro this using MvRx project.
Any additional info any of you have to help us repro this would be useful. Such as:
- Is this happening to Java as well as Kotlin tests?
- How did you start the test run exactly? Through clicking the run button at the top bar, or the run button in the gutter next to the test class/method name, or through context menu in the project view?
- Please attach idea.log of when this reproes for you.
Thanks!
Any additional info any of you have to help us repro this would be useful. Such as:
- Is this happening to Java as well as Kotlin tests?
- How did you start the test run exactly? Through clicking the run button at the top bar, or the run button in the gutter next to the test class/method name, or through context menu in the project view?
- Please attach idea.log of when this reproes for you.
Thanks!
ag...@google.com <ag...@google.com> #6
1) I ran StateStoreTest by clicking the arrow next to the class name. Tests passed
2) I changed the expected value for the first assert in testSubscribeNotCalledForNoop from 1 to 2
3) I reran the tests with control + r. Tests passed
4) I reran them again and they correctly failed (because I changed the assert)
I also ran YourKit. Out of the last 2 runs, the 2nd to last ran with out of date sources and incorrectly passed. The last run incorrectly failed.
2) I changed the expected value for the first assert in testSubscribeNotCalledForNoop from 1 to 2
3) I reran the tests with control + r. Tests passed
4) I reran them again and they correctly failed (because I changed the assert)
I also ran YourKit. Out of the last 2 runs, the 2nd to last ran with out of date sources and incorrectly passed. The last run incorrectly failed.
Description
Background: Evaluate expression in Android Studio currently uses the non-IR evaluator. That is based on the old JVM backend which will be removed. Therefore, we need to make sure that Android Studio works with the IR evaluator.
To reproduce, make sure that you run android studio with the
debugger.kotlin.evaluator.use.jvm.ir.backend=true
option.In a Kotlin Android application add the following Java code:
I.java
Consume.java
Debug the android application. At a breakpoint, evaluate the following fragment:
Evaluation fails with the message
Can not evaluate the expression: INVOKEDYNAMIC is not supported
.