Skip to content

redundancy retention of overlapping chains #92

Closed
@gsmolk

Description

@gsmolk

The problem is twofold:

  1. Redundancy retention is based on recovery-time comparison, no chain awareness. So actually expired chain can still hang around.
  2. Incremental backup just takes latest valid backup as parent, also no chain awareness.
======================================================================
FAIL: test_retention_redundancy_overlapping_chains (tests.retention.RetentionTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "tests/retention.py", line 1276, in test_retention_redundancy_overlapping_chains
    self.assertEqual(len(self.show_pb(backup_dir, 'node')), 2)
AssertionError: 5 != 2

----------------------------------------------------------------------
Ran 1 test in 24.617s

Repored by Rostislav Pochevalov

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions