Given these surprising 0-exit situations, I’m wondering:
Is restic check guaranteed to exit non-zero if an consistency issue is detected?
I believe so. In fact, it may exit with non-0 in some cases that aren’t technically errors but are simply warnings/notices, such as an unneeded partially-uploaded pack from a backup that was interrupted.
Given the information I’ve since found and documented in Exit status 0 on backup and invocation errors #2364, can @fd0 or someone familiar with the code please list the instances in which check will (and will not) exit with status 0?