Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: Shell
Labels:
None

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Certain tests such as noPassthrough/exit_logging.js intentionally crash the server and leave a core dump behind. When a task on Evg fails, regardless of which test failed the core analyzer will be triggered if a core dump is found. This means that the core analyzer is currently being triggered in cases where a random test fails and exit_logging.js happened to leave a core dump behind.

This is to have the shell clean up after tests like exit_logging.js.

is related to

SERVER-102097 Remove shell failure when unexpected core dumps are matched based on PID

Open

related to

SERVER-100559 Shell's implementation of ls attempts to call stat on symlinks

Closed

SERVER-81639 Switch windows variants from the hang analyzer to the core analyzer

Backlog

SERVER-97554 Mongo ModuleLoader's resolveBaseUrl(...) can be moved up a few layers

Backlog

SERVER-97728 Skip resmoke symbolization on test success

Closed

Assignee:: Vishnu Kaushik
Reporter:: Vishnu Kaushik
Participants:: Githook User, Vishnu Kaushik
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Nov 15 2024 08:33:26 PM UTC
Updated:: Mar 11 2025 06:38:03 PM UTC
Resolved:: Nov 22 2024 10:46:33 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates