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

Improve the scheme for test failure logging to faciliate Regex matching in BB UI

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 0
    • 2023-03-21 Ellen Ripley

      Summary
      We would like to improve the Regex matching as part of test triaging.

      Motivation

      • Does this affect any team outside of WT?
        No
      • How likely is it that this use case or problem will occur?
        This is more of an improvement, to efficiently triage the test failures.
      • If the problem does occur, what are the consequences and how severe are they?
        As we don't have any guidelines on the failure logging, each and every test case logs the failure in its own way, which makes it challenging to write the Regex in Build Baron UI. The goal is to examine the regex extracted log in the BB UI and to be able to triage the failures.
      • Is this issue urgent?
        This is more of a dev prod issue.

      Acceptance Criteria (Definition of Done)
      When will this ticket be considered done? What is the acceptance criteria for this ticket to be closed?

      • Testing
        lgtm'ed guidelines to be followed in tests for failure logging. Could provide the sample Regex to be used in BB UI. __ 
      • Documentation update
        wiki page to provide the guidelines about failure logging 

      [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

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: