Fix cache restore logic

Author: calebzulawski

index.js

@@ -192,10 +192,10 @@ async function restoreGcCache(cacheConfig) {
   // Since disk caches get updated on any change, each run has a unique key.
   // Therefore it can only be restored by prefix match, rather than exact key match.
   // When multiple prefix matches exist, the most recent is selected.
-  const restoreKey = `${config.baseCacheKey}-${cacheConfig.name}-`
+  const key = `${config.baseCacheKey}-${cacheConfig.name}-`
   await restoreCacheImpl(
-    cacheConfig, restoreKey, [restoreKey],
-    restoredKey => restoredKey.startsWith(hashedRestoreKey)
+    cacheConfig, key, [],
+    restoredKey => restoredKey.startsWith(key)
   )
 
   gc.init(cacheConfig)

post.js

@@ -81,7 +81,7 @@ async function saveGcCache(cacheConfig) {
 
   try {
     // cache already exists
-    if (await cache.restoreCache(paths, key, [], { lookupOnly: true })) {
+    if ((await cache.restoreCache(paths, key, [], { lookupOnly: true })) === key) {
       core.info('Cache already exists, skipping upload')
       return
     }