Zig-Setup is timing out in private repository on self-hosted runner

[rbarkerSL]

Problem:

I have a job running on an arc based self-hosted runner that uses this version of the setup-zig action:
mlugg/setup-zig@a67e68dc5c8281d9608136d3d7ca1b282213e4ac # v1.2.1 and times out after never completing
the download of the zig package.

We have seen this timeout frequently on our actions running in self-hosted runners in a private repository.

Description:
I see several warnings, followed by an error, followed by continued running of the setup-zig action until
the 6 hour runner time limit is exceeded and the job self-cancels.

Here is an excerpt from the attached log file that describes the situation I am seeing:

2024-11-12T21:14:17.2495781Z Fetching zig-linux-x86_64-0.13.0.tar.xz
...
2024-11-12T21:17:18.5817132Z ##[warning]Failed to restore: downloadSegmentRetry failed due to timeout
2024-11-12T21:17:18.5943199Z Cache miss. Fetching Zig 0.13.0
2024-11-12T21:17:18.5945565Z Attempting mirror: https://zigmirror.hryx.net/zig
...
2024-11-12T21:17:20.4192380Z [command]/usr/bin/tar --posix -cf cache.tgz --exclude cache.tgz -P -C /home/runner/_work/<repository name>/<repository name> --files-from manifest.txt -z
...
2024-11-12T21:17:22.2439138Z Failed to save: Unable to reserve cache with key setup-zig-tarball-zig-linux-x86_64-0.13.0, another job may be creating this cache. More details: Cache already exists. Scope: refs/heads/main, Key: setup-zig-tarball-zig-linux-x86_64-0.13.0, Version: f8c830ea35e811240be9d5006cf70b8d772b24706f3caffa189d7df216131715
2024-11-12T21:17:22.2645926Z fetch took 185015 ms
2024-11-12T21:17:22.2647687Z Extracting tarball zig-linux-x86_64-0.13.0.tar.xz
2024-11-12T21:17:22.2786844Z [command]/usr/bin/tar xJ --warning=no-unknown-keyword --overwrite -C /home/runner/_work/_temp/885627bb-afd5-44c4-a440-0cf013b2a3cf -f /home/runner/_work/_temp/zig-linux-x86_64-0.13.0
...
2024-11-12T21:17:25.0336291Z extract took 2769 ms
...
2024-11-12T21:17:30.9384399Z [command]/home/runner/_work/_tool/zig/0.13.0/x64/zig env
2024-11-12T21:17:30.9489752Z {
2024-11-12T21:17:30.9490328Z  "zig_exe": "/home/runner/_work/_tool/zig/0.13.0/x64/zig",
2024-11-12T21:17:30.9491149Z  "lib_dir": "/home/runner/_work/_tool/zig/0.13.0/x64/lib",
2024-11-12T21:17:30.9491715Z  "std_dir": "/home/runner/_work/_tool/zig/0.13.0/x64/lib/std",
2024-11-12T21:17:30.9492298Z  "global_cache_dir": "/home/runner/.cache/zig",
2024-11-12T21:17:30.9498663Z  "version": "0.13.0",
2024-11-12T21:17:30.9499377Z  "target": "x86_64-linux.5.15...5.15-gnu.2.35",
2024-11-12T21:17:30.9499906Z  "env": {
2024-11-12T21:17:30.9500560Z   "ZIG_GLOBAL_CACHE_DIR": null,
2024-11-12T21:17:30.9501016Z   "ZIG_LOCAL_CACHE_DIR": null,
2024-11-12T21:17:30.9501366Z   "ZIG_LIB_DIR": null,
2024-11-12T21:17:30.9501694Z   "ZIG_LIBC": null,
2024-11-12T21:17:30.9502419Z   "ZIG_BUILD_RUNNER": null,
2024-11-12T21:17:30.9503008Z   "ZIG_VERBOSE_LINK": null,
2024-11-12T21:17:30.9503627Z   "ZIG_VERBOSE_CC": null,
2024-11-12T21:17:30.9503979Z   "ZIG_BTRFS_WORKAROUND": null,
2024-11-12T21:17:30.9504388Z   "ZIG_DEBUG_CMD": null,
2024-11-12T21:17:30.9504788Z   "CC": null,
2024-11-12T21:17:30.9505365Z   "NO_COLOR": null,
2024-11-12T21:17:30.9505663Z   "CLICOLOR_FORCE": null,
2024-11-12T21:17:30.9505999Z   "XDG_CACHE_HOME": null,
2024-11-12T21:17:30.9506349Z   "HOME": "/home/runner"
2024-11-12T21:17:30.9506678Z  }
2024-11-12T21:17:30.9506942Z }
2024-11-12T21:17:31.6128154Z Received 42895583 of 47089887 (91.1%), 0.2 MBs/sec
....
2024-11-12T21:17:31.6128154Z Received 42895583 of 47089887 (91.1%), 0.2 MBs/sec
....
2024-11-12T21:17:31.6128154Z Received 42895583 of 47089887 (91.1%), 0.2 MBs/sec
2024-11-13T03:13:50.9349640Z ##[error]The operation was canceled.
2024-11-13T03:13:50.9477709Z Post job cleanup.

Please note that I'm seeing the output of the zig environment like I would expect to see and then it continues attempting to download the zig package.

Attached log outoput:

job32889064407_output.txt

Additional Information:

I have been attempting to duplicate the error on an example repo using github hosted runners but have not been successful yet.
example action