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

test_timestamp01 doesn't account for a large WT_TIMESTAMP_SIZE

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.12, WT3.0.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage 2017-08-21

      Description

      Steps to reproduce:

      1. Build as follows with a large timestamp (say with timestamp size 16):

      CFLAGS="-ggdb" ../configure --enable-python --enable-strict --enable-diagnostic --enable-verbose --disable-static --with-timestamp-size=16; make -j20
      

      2. Run the python test test_timestamp01:

      The following portion of the test fails:

              # Too big is also not permitted                                          
              self.session.begin_transaction()                                         
              self.assertRaisesWithMessage(wiredtiger.WiredTigerError,                 
                  lambda: self.session.commit_transaction(                             
                      'commit_timestamp=' + timestamp_str(1 << 100)),                  
                      '/too long/') 
      

      With 16 bit timestamp size, 1 << 100 is not too long. The test should look at WT_TIMESTAMP_SIZE when deciding what is too long. I am not sure how to pass that value into the python test.

        Attachments

          Activity

            People

            Assignee:
            keith.bostic Keith Bostic
            Reporter:
            sulabh.mahajan Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: