Random failures on CI when setting up Java: operation cancelled at setup-java action

[findepi]

for example in https://github.com/trinodb/trino/actions/runs/3330401482/jobs/5510058349 (#14771)
Run actions/setup-java@v3 took 59 minutes

Run actions/setup-java@v3
Installed distributions
Creating settings.xml with server-id: github
Writing to /home/runner/.m2/settings.xml
Received 0 of 936500238 (0.0%), 0.0 MBs/sec
Received 104857600 of 936500238 (11.2%), 50.0 MBs/sec
Received 255852544 of 936500238 (27.3%), 81.3 MBs/sec
Received 40[26](https://github.com/trinodb/trino/actions/runs/3330401482/jobs/5510058349#step:4:27)53184 of 936500238 ([43](https://github.com/trinodb/trino/actions/runs/3330401482/jobs/5510058349#step:4:45).0%), 95.9 MBs/sec
Received 528[48](https://github.com/trinodb/trino/actions/runs/3330401482/jobs/5510058349#step:4:50)2304 of 936[50](https://github.com/trinodb/trino/actions/runs/3330401482/jobs/5510058349#step:4:52)0238 (56.4%), 100.6 MBs/sec
Received 654311424 of 936500238 (69.9%), 103.8 MBs/sec
Received 763363328 of 936500238 (81.5%), 103.9 MBs/sec
Received 880803840 of 936500238 (94.1%), 104.9 MBs/sec
Received 932305934 of 936500238 (99.6%), 98.7 MBs/sec
Received 932305934 of 936500238 (99.6%), 88.8 MBs/sec
Received 932305934 of 936500238 (99.6%), 80.7 MBs/sec
....
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.3 MBs/sec
Received 932305934 of 936500238 (99.6%), 0.2 MBs/sec
Error: The operation was canceled.

[findepi]

cc @nineinchnick @MiguelWeezardo

[findepi]

https://github.com/trinodb/trino/actions/runs/3335340015/jobs/5520064087

[MiguelWeezardo]

My guess would be network failure on a GitHub worker. There's not much we can do to prevent this. The only solution seems to be retrying on a different worker.

[nineinchnick]

I found a quite old similar issue: actions/runner-images#4807 and then I checked the status page https://www.githubstatus.com/history. There were some incidents yesterday, but not with GitHub Actions.

[MiguelWeezardo]

This problem could be addressed by Cache segment restore timeout, unfortunately latest setup-java action uses cache action version 3.0.4 so we'll just have to wait until it's updated to 3.0.8.