Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27524

Add log message at the beginning and end of each test hook

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • Testing Infrastructure
    • None
    • Fully Compatible

    Description

      Normal tests log messages in the task logs that show the beginning and end of each test: 

      [2016/12/27 11:00:42.461] [executor:js_test:job1] 2016-12-27T16:00:42.461+0000 Running profile_geonear.js...
      		 
      ...
      		 
      [2016/12/27 11:00:45.048] [executor:js_test:job1] 2016-12-27T16:00:45.047+0000 profile_geonear.js ran in 2.59 seconds.

      This makes it easy to see which test did not finish when there is a task timeout. The hooks however, do not have log messages at their beginning and end. CleanEveryN has one at the beginning but not at the end, and the rest do not have any. We should add log messages at the beginning and end to every hook to easily diagnose hangs in them.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-26485 Refactor initial sync passthroughs to create a JSCustomBehavior instead of inheriting one

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-26522 CleanEveryN output should be written to logkeeper

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-tig DO NOT USE - Backlog - Test Infrastructure Group (TIG)
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: