Action can wait for at least 27 minutes when no progress is being made on the download

[kevinlul]

Example: https://github.com/ccmbioinfo/osmp/runs/6692774526?check_suite_focus=true

This hung on Received 1189052508 of 1193246812 (99.6%) for almost half an hour before we noticed and cancelled the workflow run.

[fl250144]

I have this errors multiple times by day...
my first thought was the cache size that was around 1.5gb... but the problem still happend even with a cache of about 150mb

[vsvipul]

@kevinlul @fl250144 Please provide full logs with step debugging enabled so that we can debug this further. Thank you.

[kevinlul]

Hello, unfortunately the bug was not reproducible, as it cleared up when we cancelled the workflow and reran it. I think the network issues that may cause this bug (e.g. GitHub API hanging) would be difficult for us to reproduce.

[vsvipul]

@kevinlul Please keep the step debugging on and provide the logs if it reoccurs anytime soon.

[fl250144]

37.zip
@vsvipul here it is
this only one example, i have more if you need.

[Kurt-von-Laven]

We have experienced this multiple times as well.

[genisd]

We have this issue as well if we use self hosted runners hosted in europe.
At the same time usiing the Github provided runners I don't get this :/

Anybody else who's getting this using own runners?

[jontze]

I encountered this behavior now as well multiple times (on github provided runners). The first time the cache download was stuck for 6 hours. As it happens only rarely non-deterministic I can't provide any debug logs nether the link to the workflow as it's a private repo.

For me this occurred during using the cache feature of actions/setup-node which internally uses actions/cache.

Logs

Run actions/setup-node@v3
with:
  node-version-file: .nvmrc
  cache: yarn
  always-auth: false
  check-latest: false
  token: ***
Resolved .nvmrc as 16
Found in cache @ /opt/hostedtoolcache/node/16.15.0/x64
/usr/local/bin/yarn --version
1.22.18
/usr/local/bin/yarn cache dir
/home/runner/.cache/yarn/v6
Received 0 of 1585939639 (0.0%), 0.0 MBs/sec
Received 83886080 of 1585939639 (5.3%), 40.0 MBs/sec
Received 222298112 of 1585939639 (14.0%), 70.7 MBs/sec
Received 348127232 of 1585939639 (22.0%), 83.0 MBs/sec
Received 494927872 of 1585939639 (31.2%), 94.3 MBs/sec
Received 612368384 of 1585939639 (38.6%), 97.2 MBs/sec
Received 713031680 of 1585939639 (45.0%), 97.0 MBs/sec
Received 817889280 of 1585939639 (51.6%), 97.4 MBs/sec
Received 910163968 of 1585939639 (57.4%), 96.3 MBs/sec
Received 1002438656 of 1585939639 (63.2%), 95.5 MBs/sec
Received 1107296256 of 1585939639 (69.8%), 95.9 MBs/sec
Received 1199570944 of 1585939639 (75.6%), 95.2 MBs/sec
Received 1296039936 of 1585939639 (81.7%), 95.0 MBs/sec
Received 1396703232 of 1585939639 (88.1%), 95.0 MBs/sec
Received 1497366528 of 1585939639 (94.4%), 95.1 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 93.9 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 88.4 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 83.5 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 79.1 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 75.1 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 71.6 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 68.3 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 65.3 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 62.6 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 60.1 MBs/sec
[.... truncated, thousand lines and several hours later...] 
Received 1577551031 of 1585939639 (99.5%), 0.1 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 0.1 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 0.1 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 0.1 MBs/sec
Received 1577551031 of 1585939639 (99.5%), 0.1 MBs/sec
Error: The operation was canceled.

As a workaround I added timeout-minutes to the steps so the workflow will at least get canceled automatically.

[kotewar]

We suspect an issue with the Azure SDK and we've opened an issue for the same here -
Azure/azure-sdk-for-js#22321

[nguyentoanit]

This happened to my repo as well. 😞