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

Suites with "archive.tests = true" always trigger core dump analyzer on test failure

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • DevProd Last Mile
    • ALL
    • Hide

      Apply archive_test_data_core_analyzer_repro.diff on commit r8.2.0-alpha-534-g1df70bc9d5f and execute a test patch with unsplittable_collections_created_on_any_shard_jscore_passthrough suite in Evergreen.

      This is an Evergreen patch example

      Show
      Apply archive_test_data_core_analyzer_repro.diff on commit r8.2.0-alpha-534-g1df70bc9d5f and execute a test patch with unsplittable_collections_created_on_any_shard_jscore_passthrough suite in Evergreen. This is an Evergreen patch example
    • DevProd Last Mile OnDeck
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Suites that are configured with "executor.archive.tests = true" always trigger core dump analyzer in case of test failure.

      I believe this is incorrect and that we should trigger the core dump analyzer only in the event of a real binary crash or hang detected.

        1. archive_test_data_core_analyzer_repro.diff
          4 kB

            Assignee:
            austin.hartschen@mongodb.com Austin Hartschen
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: