Save-grade-cache command fails when /tmp/gradle_cache_seed file does not exists. about android-orb HOT 4 CLOSED

Hi @kelvintaywl , can you explain what you were doing when this issue arose? Can you also attach a link to a build that shows this issue to confirm?

from android-orb.

Hi @kelvintaywl the /tmp/gradle_cache_seed should be generated by restore-gradle-cache . start-emulator-and-run-tests should call save-gradle-cache by default, but it also calls start-emulator which, in turn, calls restore-gradle-cache, generating the /tmp/gradle_cache_seed file. The restore-gradle-cache command has two conditions that need to be met to execute in the start-emulator command, but by default it should run. So the /tmp/gradle_cache_seed file should always be generated unless explicitly prevented by the user. Do you have any instances of this that I can use to get a bettter understanding of this issue?

from android-orb.

hi @ryanbourdais thanks for the explanation!

I understand indeed then that the hardcoded value there is assumed that the job using this save-gradle-cache command will also use the Orb's restore-gradle-cache then.
My earlier ask was since i did not notice the start-emulator command explicitly calls restore-gradle-cache!

We can close this issue i believe! Thanks for the explanation 🙏

Although I would also like to know why the save-gradle-cache command is also not included in start-emulator but outside of it?

from android-orb.

hi @kelvintaywl I will close this issue and move onto this issue I believe that save-gradle-cache is separate so that users can choose whether they want to save the cache or not, as restore will just return exit code 0 if there is no cache to restore.

from android-orb.