Don't report errors from __verify_ckptfrag_chk if verify exits early

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Verify
    • None
    • Storage Engines - Persistence
    • SE Persistence backlog
    • 3

      WT-10858 fixed spurious error message about "file ranges never verified" during verify. These occurred as a result of verify exiting the tree walk early due to another error. The first error is the real error and the "file/checkpoint ranges never verified" are just a consequence of this. WT-10858 only fixed the "file ranges never verified" message so we now need to do the same for "checkpoint ranges never verified".
      Repro:
      1. create a table
      2. inject an error in verify
      3. run verify

            Assignee:
            Jasmine Bi
            Reporter:
            Sean Watt
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: