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

Avoid stripping debug symbols from C++ unit tests in Evergreen

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.15, 3.5.2
    • Affects Version/s: None
    • Component/s: Build
    • Labels:
    • Fully Compatible
    • v3.4
    • TIG 2017-01-02

      As part of SERVER-20315, running the C++ unit tests was split out into its own unittests task. This required changes to strip the C++ unit tests, tar them up, and upload them to S3.

      With the changes from SERVER-25691, we'll now have a separate compile_all task that builds everything including the C++ unit tests. Our JavaScript integration tests (e.g. jsCore_WT) will continue to depend on the compile task that builds everything except the C++ unit tests. This means we can go back to a model where compile_all also runs the C++ unit tests, which brings the following benefits:

      • We won't need to package up the C++ unit tests and upload them to S3.
      • We won't strip the C++ unit tests to save space and will be able to run them with symbols intact to make debugging easier.

            eddie.louie Eddie Louie
            max.hirschhorn@mongodb.com Max Hirschhorn
            0 Vote for this issue
            5 Start watching this issue