hang_analyzer script should use the version of gdb from the the toolchain

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.6
    • Affects Version/s: None
    • Component/s: Build
    • None
    • Fully Compatible
    • ALL
    • Hide

      Write a c++ unit test that sleeps for several hours.
      Set the timeout_secs in the compile phase to a smallish value, like 120, in evergreen.yml
      Run a patch build through evergreen, and examine the hang analyzer output for your sleeping test.

      Show
      Write a c++ unit test that sleeps for several hours. Set the timeout_secs in the compile phase to a smallish value, like 120, in evergreen.yml Run a patch build through evergreen, and examine the hang analyzer output for your sleeping test.
    • Build 5 06/26/16, Build 6 07/17/15
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The hang analyzer script finds gdb in the path, and our evergreen configuration doesn't add the mongodb toolchain to the path, so we end up running the gdb from /usr/bin. On the Linux64 build variant, gdb is too old to read the debug information from our tool chain, so the hang analyzer produces useless output.

      We should change either evergreen.yml or the hang analyzer to use the appropriate gdb for the toolchain.

            Assignee:
            Jonathan Reams
            Reporter:
            Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: