From c349fa5b1f789c6d45979b48e470ffdb61e2f4a5 Mon Sep 17 00:00:00 2001
From: Daz DeBoer <daz@gradle.com>
Date: Wed, 19 Jan 2022 13:31:55 -0700
Subject: [PATCH] Do not hide ReserveCacheError failures

When the target entry already exists, we are unable to save. Ensuring this situation
is logged helps make the logs more understandable.
---
 src/cache-utils.ts | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/src/cache-utils.ts b/src/cache-utils.ts
index 13402ab..7ff303e 100644
--- a/src/cache-utils.ts
+++ b/src/cache-utils.ts
@@ -99,11 +99,7 @@ export function handleCacheFailure(error: unknown, message: string): void {
     }
     if (error instanceof cache.ReserveCacheError) {
         // Reserve cache errors are expected if the artifact has been previously cached
-        if (isCacheDebuggingEnabled()) {
-            core.info(`${message}: ${error}`)
-        } else {
-            core.debug(`${message}: ${error}`)
-        }
+        core.info(`${message}: ${error}`)
     } else {
         // Warn on all other errors
         core.warning(`${message}: ${error}`)