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

Reduce concurrency for Windows compile_all builds to avoid OOM failures

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.12
    • Component/s: Build
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      TIG 2017-08-21
    • Linked BF Score:
      0

      Description

      The compile_all task has been failing intermittently for more than 2 months (https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_debug_compile_all_8cd6e2a8af540bbea188c98cfae9139b400af83c_17_05_25_01_44_18 is an early occurrence). We've attempted to increase the amount of memory available on the machine but are still seeing cases where the many linker processes report they are out of memory. Andrew Morrow suspects the problem could be resolved by adjusting the link graph to avoid having so many C++ unit tests depend on the mongo/db/serveronly library. Until such a project can scheduled, we should reduce the value for the --jobs option specified to SCons when our Windows builders are running the compile_all task to avoid further Evergreen failures.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: