Loading...

XML

Word

Printable

JSON

Assigned Teams:

DevProd Last Mile
Operating System:
ALL
Steps To Reproduce:

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
Confidence Status:
None
Work Order:
3
CAR Domain/s:
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.

causes

SERVER-105105 Link to core analyzer task is no longer attached to failing Evergreen task

related to

SERVER-103440 Unset test archival from unsplittable_collections_created_on_any_shard_jscore_passthrough suite

SERVER-104588 Only run core analysis on core dumps produced by MongoDB process crashes and Evergreen timeouts

Assignee:: Austin Hartschen
Reporter:: Tommaso Tocci
Participants:: Austin Hartschen, Githook User, Max Hirschhorn, Tommaso Tocci
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue