C++ Integration Test Binaries are not archived on failure/when core-dumps are taken

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Development Platform
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In tasks like this one, which run C++ integration tests, core dumps are correctly collected on crashes and hangs. However, because the C++ integration tests binaries are not archived independently, and because they are skipped by this condition in failed_unittest_gather.sh , the integration test binaries from which the core dumps are taken are not archived anywhere. This means they aren't accessible on spawnhosts for the task, etc, and means that the core dumps are essentially useless unless a server engineer can rebuild the binary from source on the spawnhost. I would like if we archived the integration test binaries so they fit into the same debugging workflow used for coredumps from server binaries and unittest binaries.  

            Assignee:
            Trevor Guidry
            Reporter:
            George Wangensteen (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: