Fixed
Status Update
No update yet.
Comments
aa...@google.com
je...@google.com
I am also on Catalina if it helps.
mi...@google.com
I'm also affected but I'm on Windows10. can confirm it on version 4.0 Canary 9
se...@exaring.de
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
mi...@google.com
se...@exaring.de
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!
se...@exaring.de
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.
hu...@google.com
Thanks, I'm able to repro this now.
mi...@google.com
hu...@google.com
Any update or workaround here? It's extremely error prone to work when you don't know what version of the source Android Studio is using.
an...@google.com
This seems to be an issue where the Gradle plugin does not see up to date sources, maybe due to VFS freshness. Jerome, anyone in Build team can help take a look?
Description
Note: This is a bug in the Android Gradle Plugin, but I am not allowed to create an issue in the Android Gradle Plugin component.
ISSUE:
The
AidlCompileAndroid Gradle Plugin task is rarely, and completly randomly, failing with the exceptionIndexOutOfBoundsException: Index 0 out of bounds for length 0. See also the below stacktrace.Re-runing the same Gradle command, with the same input, always resolves this issue. Sometime we have to re-run multiple times though.
Because this issue appears randomly, and for a while now, it is hard for us to pinpoint the exact versions when this issue first appeared.
Currently we use APG 8.2.0 with Gradle 8.5 and build-tools 34.0.0.
We experience this issue only on our CI where all builds are running inside a separate docker container, and are therefore de-facto clean builds. However we are re-using the Gradle build-cache across our different stages. But the Gradle daemon is alwas spawned anew.
We only have one AIDL file, which is only in the sourceset of our
AndroidTVflavor:app/src/androidtv/aidl/com/example/FunInterface.aidl. And our project has a lot of app variants. There are two buildTypes (debug, release) and four product flavor dimensions (one dimension isplatformwhereAndroidTVis one of the flavors).Even though we enabled AIDL compilation for all variants it only fails when running
assembleAndroidTV...Releasefor theAndroidTVflavor.From what I understand the cause for this issue is that the AIDL output files are seemingly empty. However, after the job failed there is one valid Java file inside
app/build/generated/aidl_source_output_dir/androidtvInternalStandaloneProdRelease/out/com/example/FunInterface.java.STEPS TO REPRODUCE:
The build failure happens randomly and rarely, therefore I am not able to provide neither steps to reproduce nor an explicit repro-sample project.
VERSIONS:
Version of Gradle Plugin: 8.2.0
Version of Gradle: 8.5
Version of Java: OpenJDK 64-Bit Temurin-17.0.8+7
OS: Ubuntu 22.04.2 LTS