test(postgres): describe what the backup deadline test still guards

The deadline no longer applies to a failed cnpg.io/Backup, which now
fails its BackupJob at once; it only bounds the wait for the
barman-cloud plugin rollout, and the comment still claimed the former.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
This commit is contained in:
Alexey Artamonov committed 2026-11-09 23:52:25 +03:00
1 parent 7efe33e87d
commit 8061e2dbd9
1 file changed
+3 -4
@@ -1000,10 +1000,9 @@ func TestUnmarshalCNPGBackupSnapshot_RejectsMissingOrWrongKind(t *testing.T) {
}
}
// TestCNPGBackupDeadlineExceeded locks in the wall-clock cap that prevents a
// perpetually-failed cnpg.io/Backup from pinning the BackupJob in Running
// forever. Without this guard the Plan-controller queue would back up
// behind a single broken backup.
// TestCNPGBackupDeadlineExceeded locks in the wall-clock cap on waiting for
// the barman-cloud plugin rollout, so a rollout that never finishes fails the
// BackupJob instead of pinning it in Running.
func TestCNPGBackupDeadlineExceeded(t *testing.T) {
cases := []struct {
name string