[Gluster-infra] [Bug 1491156] Aborted test runs in jenkins don't have cores

2018-04-12 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1491156 Nigel Babu changed: What|Removed |Added Status|NEW |CLOSED

[Gluster-infra] [Bug 1491156] Aborted test runs in jenkins don't have cores

2017-09-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1491156 --- Comment #4 from Niels de Vos --- (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

[Gluster-infra] [Bug 1491156] Aborted test runs in jenkins don't have cores

2017-09-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1491156 --- Comment #3 from Nigel Babu --- Is there a preferred command to get the right PID? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug

[Gluster-infra] [Bug 1491156] Aborted test runs in jenkins don't have cores

2017-09-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1491156 --- Comment #2 from Niels de Vos --- (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

[Gluster-infra] [Bug 1491156] Aborted test runs in jenkins don't have cores

2017-09-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1491156 --- Comment #1 from Nigel Babu --- 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? -- You are receiving this mail because: You are on the

[Gluster-infra] [Bug 1491156] Aborted test runs in jenkins don't have cores

2017-09-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1491156 Raghavendra G changed: What|Removed |Added Assignee|b...@gluster.org|nig...@redhat.com