Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-12030

Make config_compare more robust in test_import_base

    • Storage Engines
    • 5
    • 2024-01-09 - I Grew Tired

      The test test_import01.py can be easily broken with the following diff:

      diff --git a/test/suite/test_import01.py b/test/suite/test_import01.py
      index 73d36e2b68..62af5e09ce 100644
      --- a/test/suite/test_import01.py
      +++ b/test/suite/test_import01.py
      @@ -169,6 +169,7 @@ class test_import01(test_import_base):
       
               # Import the file.
               self.session.create(self.uri, import_config)
      +        self.session.checkpoint("name=abc")
       
               # Verify object.
               self.verifyUntilSuccess(self.session, self.uri, None)
      

      There is an existing config_compare function that is supposed to parse and compare metadata information but it does not do well with named checkpoints. It does strip out the "checkpoint" section of the metadata file in a way that is okay because the test does not contain named checkpoints. But adding one before comparing the configurations would make the test fail while it should pass.

      This ticket should:

      • Fix config_compare to take into account named checkpoints
      • Add named checkpoints to the test to verify the fixed function works

            Assignee:
            mariam.mojid@mongodb.com Mariam Mojid (Inactive)
            Reporter:
            etienne.petrel@mongodb.com Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: