Failure to restore cache causes the GitHub Action step to run indefinitely about composer-install

[cvergne]

That's really strange as actions/cache@v3 has 2 timeout (since at least 4 months now) :

1. 1 hour for the entire download
2. 10 minutes for each download segment of 128MB

So your step should have been stopped after max 1 hour (even 10 minutes if it was a segment stuck).

Anyway, the segment timeout can be configured on actions/cache with env var SEGMENT_DOWNLOAD_TIMEOUT_MINS (default to 10 min), but I'm not sure if it is handled without any change into composer-install action.

Edit: that comment is because I had the same problem, except the cache action had a timeout after 10 minutes.

[ghostwriter]

It happened again, timed out after 6 hours.

[ramsey]

What does “closed as not planned” mean?

[ghostwriter]

"Closed as not planned" is just GitHub UI string.

In this case, the issue was closed because there was no response from you (the author), at all, and it was deemed by us as stale and unreproducible now based on the information available in the GitHub logs.

I assure you that I have no alternative motives or hidden intentions.

The alternative would mark this issue as resolved.

Additionally, I no longer have this issue and do not want to keep it open.

[ramsey]

Oh, interesting. I didn't realize they had added that to the "close" button.

I had not been able to reproduce this, so I was waiting to see if others found this issue and reported they were experiencing similar things.

So, to confirm, you're no longer able to reproduce this?

[ghostwriter]

That is correct.

Something is still causing this to run for up to 6 hours, but I personally am no longer able to reproduce this.

https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#usage-limits

Job execution time - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.

[ramsey]

Do you think the problem that causes it to run that long is in this project or somewhere else?

[ghostwriter]

The problem that causes it to run that long is not in this project, it's in actions/cache.

However, this project runs actions/cache internally and the issue here is not properly handling actions/cache issues.

As stated above,

https://github.com/actions/cache/blob/f7ebb81a3f195b4fb88dab7c14e2f7aff52045aa/README.md#L26-L28

• Fixed the download stuck problem by introducing a timeout of 1 hour for cache downloads.
• Allowed users to provide a custom timeout as input for aborting download of a cache segment using an environment variable SEGMENT_DOWNLOAD_TIMEOUT_MINS. Default is 10 minutes.

eg. There is currently no way to use SEGMENT_DOWNLOAD_TIMEOUT_MINS using this project.