[Gluster-devel] [regression tests] Aborted runs and diagnostic information

Nigel Babu nigelb at redhat.com
Wed Sep 28 12:58:11 UTC 2016

We don't collect any information before aborting tests. However, if we can
put together a list of things we'd like to do collect before aborting jobs,
I can look into what can be done to collect it.

On Wed, Sep 28, 2016 at 4:19 PM, Raghavendra Gowdappa <rgowdapp at redhat.com>

> Hi all,
> Do we collect any diagnostic information before aborting tests as in [1]?
> If yes, where can I find them?
> If no, I think following information would be useful
> 1. ps output of all relevant gluster processes and tests running on them
> (to find status of processes like 'D' etc)
> 2. Statedump of client and brick processes (better to dump all information
> like inodes, call-stack, etc)
> 3. coredump of client and brick processes
> If you think any other information is helpful, please add to the list.
> In the specific case of [1], the test runs fine on my local machine, but
> always hangs on build machines. So having this information is helpful.
> [1] https://build.gluster.org/job/netbsd7-regression/886/console
> regards,
> Raghavendra

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160928/36771aeb/attachment.html>

More information about the Gluster-devel mailing list