[Android] setup-gradle: After canceling build - Could not read workspace metadata from C:\Users\runneradmin\.gradle\caches\transforms-4\0e69aaacf4af78f6c6c3f80936fa8b36\metadata.bin

[david-allison]

Description

main branch: After cancelling a workflow, we encountered the following error on our next CI run

Execution failed for task ':AnkiDroid:checkPlayDebugAarMetadata'.
> A build operation failed.
      Could not read workspace metadata from C:\Users\runneradmin\.gradle\caches\transforms-4\0e69aaacf4af78f6c6c3f80936fa8b36\metadata.bin
   > Could not read workspace metadata from C:\Users\runneradmin\.gradle\caches\transforms-4\0e69aaacf4af78f6c6c3f80936fa8b36\metadata.bin

I suspect that this is an instance of #71. I have done no further diagnostics and this may be related to another part of our CI

• Cache cleanup should not run for failed jobs #71

---

Workaround

We used cache-disabled: true as a temporary workaround

• ankidroid/Anki-Android@f9b7ee6

---

Additional information

gradle/actions/setup-gradle@v3 on GitHub Actions (windows-latest).

• gradle/[email protected] (SHA:1168cd3d07c1876a65e1724114de42ccbdfa7b78)
• gradle-wrapper: 8.7
• gradle-home-cache-cleanup: true

setup-gradle@v3 YML

      - name: Setup Gradle
        uses: gradle/actions/setup-gradle@v3
        timeout-minutes: 5
        with:
          # Only write to the cache for builds on the 'main' branches, stops branches evicting main cache
          # Builds on other branches will only read from main branch cache writes
          # Comment this and the with: above out for performance testing on a branch
          cache-read-only: ${{ github.ref != 'refs/heads/main' }}
          gradle-home-cache-cleanup: true

The workflow on main was cancelled due to another pull request being merged

@bogdanzurac has also reported this is occurring on private repos on their company's CI [Linux]

@david-allison We've been experiencing this issue on some of our internal projects as well. While searching for this issue online, this is the only other reference I could find.

From what I can see, you're using Windows CI + updated recently to Gradle 8.7. Our CI runs Linux and Gradle 8.6/8.7 and we're also encountering the same problem. When have you first started seeing this? Does it only happen on CI or locally as well? Does it only happen when running unit tests?

ankidroid/Anki-Android#16161 (comment)

---

Links

• https://github.com/ankidroid/Anki-Android/commits/main/.github/workflows/tests_unit.yml
  • Workflow history (main): https://github.com/ankidroid/Anki-Android/actions?query=branch%3Amain
    • Last success
    • Cancelled workflow
    • First failure
• Issue
  • Ci Failure (Windows-unit tests): Could not read workspace metadata from C:\Users\runneradmin\.gradle\caches\transforms-4\0e69aaacf4af78f6c6c3f80936fa8b36\metadata.bin ankidroid/Anki-Android#16161
• We previously had an issue with the transform cache
  • Immutable workspace contents have been modified with current gradle (8.6) and this action #47

[bigdaz]

@david-allison I'm pretty sure that cache-cleanup cannot be responsible here, since Gradle 8.7 doesn't perform any cleanup of the caches/transforms-4 directory (#47).

But to be certain, can you please remove gradle-home-cache-cleanup from your workflows, and re-enable the cache?

You may need to remove the offending cache entries, which you can see if you inspect the Job Summary here. In essence, you need to purge any entries starting with v9-gradle|Windows|unit[b9fd878989bfb04c13e5cd621616f3df].
You can delete these easily via the UI.

[david-allison]

Thanks for the response. gradle-home-cache-cleanup disabled: ankidroid/Anki-Android#16165.

Cache already appeared to be empty of Windows-related entries. Will let you know if there are additional failures

I mostly added this issue for documentation. Obviously happy to close if my assertions are incorrect. Thanks for your time!

[bigdaz]

Thanks for the report. This actually came up internally at Gradle today, where this error was encountered outside of the context of GitHub Actions. So your report was timely and useful.

[bigdaz]

@david-allison I'll close this issue for now. Please let us know if you see further failures with gradle-home-cache-cleanup disabled, and we can re-open it.

[david-allison]

No failures since (thank you!), but will keep you informed and am happy to close

We'll move back to gradle-home-cache-cleanup when it's no longer experimental