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

Failed: recovery-stress-test on Ubuntu 18.04 zSeries [WiredTiger (develop) @ ad3eae09]

    • Type: Icon: Build Failure Build Failure
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None

      recovery-stress-test failed on Ubuntu 18.04 zSeries

      Host: ubuntu1804-z-13.dallasisv.build.10gen.cc
      Project: WiredTiger (develop)
      Commit: diff: WT-5671 Implement committed prepared transactions with durable history (#5411)

      With this change, the committed prepared updates are written to the data store to ease the cache pressure. Along with the above change, there are a couple of fixes done to use the proper durable timestamp in the history store updates.

      • Do not yet enable the Python prepare test.
      • Remove unused code.
      • Removed unused code.
      • Merge fixes and use the same variable notation of start/stop durable timestamps
      • Some fixes to use the proper durable timestamp
      • clang analyzer fixes
      • Remove some fixes that are covered already
      • Revert the changes from of ticket 5978
      • reorganize the durable timestamp selection and comments update
      • Save durable timestamp for history store update and other changes
      • Don't set selected update to NULL even if it is globally visible
      • Remove a double assignment that is not needed
      • Variable declaration rearrangements and additional asserts
      • Mask the clang analyzer output as it was masked earlier also

      Co-authored-by: Haribabu Kommi <haribabu.kommi@mongodb.com> | 15 Apr 20 22:40 UTC
      Evergreen Subscription: ; Evergreen Event:

      Task Logs

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            xgen-evg-user Xgen-Evergreen-User
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: