Multiversion tests failing due to data format change in durable history

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Execution Team 2020-03-09, Storage Engines 2020-03-23, Storage Engines 2020-04-06
    • 3

      The multiversion evergreen suite appears to expect in various tests that you can run 4.4 on a previous (before 4.2) version. However currently this can result in 4.4 altering the metadata file and making it unreadable for previous version. Is it reasonable to update the multiversion test suite to change this expectation?

      One test in particular is the mulitversion/skip_level_upgrade.js test, which intentionally skips levels when running mongod.

              Assignee:
              Luke Pearson
              Reporter:
              Luke Pearson
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: