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

test/format stress sanitizer key mismatch

    • Type: Icon: Task Task
    • Resolution: Done
    • WT2.5.3
    • Affects Version/s: None
    • Component/s: None

      Last night we had this failure on tinderbox

      http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-sanitizer/2804/

      nextprev: next key mismatch:
      	bdb-key {0000090875.07/opqrstuvwxyzabcdefghijklmnopqr}
      	 wt-key {0000090876.00/opqrstuvwxyzabcde}
      

      Here's the CONFIG:

      ############################################
      #  RUN PARAMETERS
      ############################################
      abort=0
      auto_throttle=1
      firstfit=0
      bitcnt=6
      bloom=1
      bloom_bit_count=26
      bloom_hash_count=18
      bloom_oldest=0
      cache=90
      checkpoints=1
      checksum=uncompressed
      chunk_size=3
      compaction=1
      compression=none
      data_extend=0
      data_source=lsm
      delete_pct=2
      dictionary=0
      evict_max=2
      file_type=row-store
      backups=0
      huffman_key=0
      huffman_value=0
      insert_pct=76
      internal_key_truncation=1
      internal_page_max=17
      isolation=random
      key_gap=0
      key_max=64
      key_min=30
      leak_memory=0
      leaf_page_max=17
      logging=1
      logging_archive=1
      logging_prealloc=0
      logging=1
      lsm_worker_threads=3
      merge_max=12
      mmap=1
      ops=100000
      prefix_compression=1
      prefix_compression_min=1
      repeat_data_pct=2
      reverse=0
      rows=100000
      runs=1
      split_pct=52
      statistics=1
      threads=1
      timer=0
      value_max=458
      value_min=19
      wiredtiger_config=
      write_pct=41
      ############################################
      

            Assignee:
            Unassigned Unassigned
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: