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

Restore consistency for whether resmoke tests are run out of git repository or not in Evergreen

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Correctness

      The changes from 9f4d474 as part of SERVER-91567 made it so the 10gen/mongo repository would be cloned prior to running tests with resmoke. This step was necessary for some of the code coverage tooling which required a git checkout. However the current behavior is misleading because other build variants require test files to be explicitly included in the Artifacts tarball. Worse still is the condition for whether or not to clone the git repository is based on whether the gcov_tool Evergreen expansion is defined and results in sanitizer build variants cloning the git repository even when they aren't running any code coverage related Evergreen tasks.

            Assignee:
            Unassigned Unassigned
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: