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

Prevent ninja from printing entire bazel build rule outputs when there is a compile error

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible

      Currently when compiling with ninja, the entire build rule output is emitted on failure. When the build rule is invoking bazel, this means that all of the bazel build outputs (half our build) are emitted following the actual compile error. This means that there are often many pages of texts enumerating all the files/libraries bazel is compiling hiding the actual error, which is confusing for developers and requires scrolling past to hunt for the actual error. It's particularly confusing for new team members. 

       

      Here is an example of all of the output from a simple compile failure with ninja (the actual failure is calling a private member function not visible to the caller): 

      https://docs.google.com/document/d/1iMGdEIj6DkLwHmZBecAdEOVTNBKEthEXotls0edyQys/edit 

            Assignee:
            daniel.moody@mongodb.com Daniel Moody
            Reporter:
            george.wangensteen@mongodb.com George Wangensteen
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: