When initially migrating a repo to use Ploutos the config you use won't be perfect or won't work at all and will need refining. However, even if the first action run installed dependent s/w such as cargo-deb and cargo-generate-rpm, subsequent runs while refining will redo those slow install steps. This is because actions/cache won't save the installed s/w to cache if the job fails.

This is a known issue with actions/cache. Recently actions/cache#1020 proposed a solution, for us this would meaning using the new actions/cache/save action, once it becomes available, to save the cache earlier in the job.