Description of problem: When CI fails with a coredump, it'll be possibly useful to save that core dump for a more thorough investigation. Example - https://build.gluster.org/job/centos7-regression/5473/ There is just /var/log/glusterfs files there. Would it be possible to run perhaps abrt-action-analyze-backtrace to get a better result?
We do archive the core file at a centarlized log server. For the given regression build: https://logs.aws.gluster.org/centos7-regression-5473.tgz (build/install/cores/file) I need to look more abrt-action-analyze-backtrace and it can be implemented.
(In reply to Deepshikha khandelwal from comment #1) > We do archive the core file at a centarlized log server. > > For the given regression build: > https://logs.aws.gluster.org/centos7-regression-5473.tgz > (build/install/cores/file) Yes, I just saw it now in the console of the Jenkins job. I believe the instructions there how to use gdb to look at it are outdated, btw. > > I need to look more abrt-action-analyze-backtrace and it can be implemented. I couldn't get it - but perhaps on the machine itself its doable.