It's the coq project this time.
Is it just me, or does your software just give up forever after a failed update? Would it not make sense to add the repository at the end of the queue of repositories to check for updates?
Another one stuck at "Step 1 of 3: Downloading source code history (Failed)"
about 1 year ago
about 1 year ago
I've rescheduled the update.
There are many types of errors that require manual rescheduling, but there are a lot of errors that our system will automatically re-attempt after a delay.
Over time, we are slowly expanding the number of error types that we automatically reschedule. Going forward, you won't see as much of the "give up forever" behavior as before.
This particular job failed because of a permissions failure, which is something we don't currently auto-retry. I'll keep an eye on it.
Thanks, Robin