Bug 1491156
Summary: | Aborted test runs in jenkins don't have cores | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Raghavendra G <rgowdapp> |
Component: | project-infrastructure | Assignee: | Nigel Babu <nigelb> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | bugs, gluster-infra |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-12 15:02:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Raghavendra G
2017-09-13 08:09:20 UTC
I'm guessing this means it wasn't a crash. The best way to do this would be to attach gdb to the process to generate the core, yes? (In reply to Nigel Babu from comment #1) > I'm guessing this means it wasn't a crash. The best way to do this would be > to attach gdb to the process to generate the core, yes? That, or run 'gcore $PID' and 'gstack $PID' to make it a little easier. Is there a preferred command to get the right PID? (In reply to Nigel Babu from comment #3) > Is there a preferred command to get the right PID? I don't think so, that would require guessing what process hangs. You probably need to capture the stack+core from all gluster processes. We will no longer have hangs because of the per patch timeout. Closing this bug. |