Fixed
Status Update
No update yet.
Comments
al...@google.com
al...@google.com
Once this bug is fixed, we can close
jl...@j3ltd.com
The description of 75991 is vague enough to be classified as ongoing and never going to be resolved.
So my understanding is no there are no plans to resolve
Maybe someone at Google has a better insight into the issue processing process?
p....@blueesoteric.com
As far as the underlying IntelliJ bug for the merged https://youtrack.jetbrains.com/issue/IDEA-91952
al...@google.com
ls...@google.com
uc...@google.com
jr...@squareup.com
Here's an example where running through the Gradle tooling API would have been useful: https://github.com/cashapp/paparazzi/pull/125
Any updates here? It's a bit of cognitive load to have different developer experiences on CLI vs IDE builds.
Any updates here? It's a bit of cognitive load to have different developer experiences on CLI vs IDE builds.
ph...@monzo.com
Having no way to hook into IDE test execution from build files is pretty painful.
I used -javaagent trick from this blog post
hu...@google.com
Android Studio now delegats unit test executions to Gradle starting in Arctic Fox and it also delegates instrumented tests starting in BumbleBee.
[Deleted User] <[Deleted User]>
From
on 15/10/2022: issue 36988115
$ jps -mv | grep studio 37605 -Dfile.encoding=UTF-8 -ea -Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true -Djna.nosys=true ...
Description
This is a general bug encapsulating all the features needed (meant to flag external reports as duplicate of this one).
Things to look for:
- Specifying which device to run on through the tooling API.
- Getting results and displaying it in IJ, whether for one or more devices.