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

resmoke.py should retry getting a build_id and test_id from logkeeper

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      TIG 2018-07-30, TIG 2018-08-13
    • Linked BF Score:
      16
    • Story Points:
      2

      Description

      The changes from SERVER-35472 made it so that resmoke.py would exit if it couldn't communicate with logkeeper. This has lead to setup failures in Evergreen that are caused by the logkeeper application server not responding with a build_id or test_id quickly enough. It might be that retrying would succeed that we should make 10 attempts and fail if we still don't get a build_id or test_id.

      Note: Retrying the request to get a build_id or new test_id is safe as it simply inserts a new document. The only quirk is that the "Job logs" tab may show extra entries in the case that resmoke.py never received a response from the logkeeper application server but the database still eventually did the work.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: