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

Add non-standalone Evergreen tests

    • Storage Engines - 2022-11-14

      Summary
      What is the problem or use case, what are we trying to achieve?
      All the WiredTiger testing is executed in for builds in WiredTiger standalone mode. Hence by default the flag "fast_truncate_2022" is set to true. There is no WiredTiger level testing by setting this flag as false. The flag "fast_truncate_2022" is introduced as part of supporting truncate operation with timestamp and to control the data format change associated with it.

      Motivation

      • Does this affect any team outside of WT?
        (Are they blocked? Are they waiting for an answer?)
        For MongoDB builds, this flag will be set as false, and hence none of the WiredTiger tests currently exercising the truncate operation the way MongoDB is currently using.
      • How likely is it that this use case or problem will occur?
        (Main path? Edge case? Frequency of the issue?)
        Most likely, as currently there is no testing for truncate operations the way MongoDB is using.
      • If the problem does occur, what are the consequences and how severe are they?
        (A minor annoyance at a log message? Performance concern? Outage/unavailability? Test Failure?)
        Not having test coverage is a problem, will greatly limit our ability to uncover bugs.
      • Is this issue urgent?
        (Does this ticket have a required timeline? What is it?)
        Relatively urgent.

      Acceptance Criteria (Definition of Done)
      (When will this ticket be considered done? What is the acceptance criteria for this ticket to be closed?)
      Test coverage is subjective, when the ticket is scheduled the work to be outlined and get an agreement.

      • Testing
        (What all testing needs to be done as part of this ticket? Unit? Functional? Performance?Testing at MongoDB side?)
        None, as this itself is improving testing.
      • Documentation update
        (Does this ticket require a change in the architecture guide? If yes, please create a corresponding doc ticket.)
        None

      [Optional] Suggested Solution
      (Is there any suggested solution to handle this issue? Is it related to any existing WT ticket? Is it related to any previous issue fixed? If yes, link the WT ticket number using related to, depends on, dependent on by links)
      Test format could be modified to exercise truncate with out timestamps.

            Assignee:
            chenhao.qu@mongodb.com Chenhao Qu
            Reporter:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: