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

resmoke.py shouldn't fall back to stderr when logkeeper is unavailable

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0, v3.6, v3.4, v3.2
    • Sprint:
      TIG 2018-06-18
    • Linked BF Score:
      25

      Description

      The Evergreen team believes that having resmoke.py fall back to writing the test output to its stderr (and therefore to the "task logs") puts too much pressure on the Evergreen database when logkeeper is unavailable. We would rather discard the test results of an Evergreen task if we fail to record any log messages to the logkeeper rather than try to preserve the test results and record log messages to the Evergreen database.

      We can reuse the mechanism from SERVER-32121 to cause the Evergreen task to turn purple should resmoke.py find that logkeeper is unavailable.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              max.hirschhorn Max Hirschhorn
              Reporter:
              max.hirschhorn Max Hirschhorn
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: