Cache miss with Gradle 8.0.1 and KGP 1.8.10

[cdsap]

Kotlin Compiler tasks generate different build cache key when building different architectures(aarch64,amd64)

Expected Behavior

Both tasks generate the same Build Cache key

Current Behavior

Tasks generate different build cache key

Gradle 7.6 generates same Build Cache key

Context

Steps to Reproduce

1- Download repository https://github.com/cdsap/kotlin-caching
2- Execute in MacOs(aarch64) :lib:compileKotlin
3- Execute in Linux(amd64) :lib:compileKotlin
4- Compare inputs for both tasks

Your Environment

Build scan comparison 8.0.1: https://ge.solutions-team.gradle.com/c/r77tmf6f3plo6/ugx5xkgns2rme/task-inputs
Build scan comparison 7.6: https://ge.solutions-team.gradle.com/c/6rcapxnybkaja/kivlrtkxrsxy2/task-inputs

[lwasyl]

Corresponding bug on Youtrack side for reference: https://youtrack.jetbrains.com/issue/KT-56929/Kotlin-tasks-not-cacheable-between-architectures

[AndreasTu]

This is maybe the same bug as #24031

[eskatos]

Thank you for your interest in Gradle!

This issue will be closed as a duplicate of

• InstrumentingTransformer generates different class files in Gradle 8 and 7.6 which leads to Remote Build-Cache misses #24031

Please add your use case and 👍 to that issue.

[lwasyl]

@eskatos Just to make sure, are you positive this is a duplicate of #24031? That issue is about different cache keys between different Gradle versions, the problem here doesn't involve Gradle 7.6 at all, it's about different cache key different OSes/architectures, and the same Gradle version is used on both of them 🤔

[eskatos]

@lwasyl yep positive
The issue report has links to 7.6 build scans where this was working, this is what hinted at this being the same as #24031.
I could not reproduce with clean systems but could reproduce as soon as I ran builds with 7.6 beforehand.