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

test/format key out of order failure

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • 13
    • Storage Engines 2020-01-13, Storage Engines 2020-01-27, Storage Engines 2020-02-10

      While trying to reproduce WT-5119, I hit a key out of order failure instead. This was running 5 parallel processes on ocelot-aws. It was running with the 5119.Dec16.diff applied and the develop branch as of Dec 16, changeset 2d2e285. It hit after nearly 2700 iterations (and two other machines have not hit it but they're running an older develop rev).

      The error is:

      t: FAILED: next returned {0000077127.00/opqrstuvwxyzabcdef} then {0000000001.00/opqrstuvwxyzabcdefgh}
      

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: