This message was deleted.
# community-support
s
This message was deleted.
d
If you mouse or click over what is highlighted (can’t remember which right now and don’t have a scan to go off of), you’ll get the differences between a/b. It’ll have the file paths on both machines, you’ll need to download them and diff them to see what’s going on. from there you can exclude items if they aren’t important. Also, if you haven’t added this to your project test, I’d do that first then look at misses - https://github.com/gradle/android-cache-fix-gradle-plugin
k
yep, we do have that plugin in place 🙂 Thanks for the tip on downloading the folders….probably would be a good idea to put that in the help popup for that buildscan UI too.
Interesting:
Copy code
diff -r extracted /tmp/extracted
Only in /tmp/extracted/java.base: NOTICES
Binary files extracted/java.base/java/lang/invoke/DelegatingMethodHandle$Holder.class and /tmp/extracted/java.base/java/lang/invoke/DelegatingMethodHandle$Holder.class differ
Binary files extracted/java.base/java/lang/invoke/DirectMethodHandle$Holder.class and /tmp/extracted/java.base/java/lang/invoke/DirectMethodHandle$Holder.class differ
JDK is the same on both CI agent and our laptops. Interesting that this file differs because it’s a java.lang.invoke class…
d
ran into the same item, which lead to this sort of item being added to the allProjects
Copy code
allProjects {
  normalization {
    runtimeClasspath {
      ignore '**/module-descriptor.txt' // don't need if you are up to date on AGP cache plug in fix
      ignore '**/java/lang/invoke/**'
    }
}
thank you 1
v
Diff the directories using IntelliJ and you should usually also see the diff of the decompiled class files unless it is just in some metadata
k
@Daniel B Duval out of curiosity, which JDK are you using for CI vs. dev machines? We’re using an internal one built off openjdk11…I showed this to our VM folks and they’re puzzled that the generated bytecode is different for x86 vs. ARM (the Holder class is generated by the JVM via generation of JVM bytecode)…
d
Liberica arm64 for macs with M1 chips. Open jdk 11 for Mac books with intel. All CI machines are m1. Engineers may have intel or m1
k
Similar except our CI machines are linux. Thanks! (trying to convince the gradle cache plugin folks to fix this there so other folks don’t need the temporary workaround we have)
d
Did you try with 2.5.6 and compare to another not using 2.5.6 but earlier? 2.5.6 was addressing part of what I put I up. I haven’t updated since that got addressed
k
I checked the gradle cache plugin 2.5.6 source code and it doesn't handle this. I filed an issue so maybe the next one will... 🙂
d
I’m aware 😉
🙂 1