<div dir="ltr"><div><div><div>Hi Atin,<br><br></div>Have a check at current version of regression.sh here:<br><br><a href="https://forge.gluster.org/gluster-patch-acceptance-tests/gluster-patch-acceptance-tests/blobs/master/regression.sh">https://forge.gluster.org/gluster-patch-acceptance-tests/gluster-patch-acceptance-tests/blobs/master/regression.sh</a><br><br></div>It should be a small patch near to line 109.<br><br></div>--Humble<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>--Humble<br></div><br></div></div></div>
<br><div class="gmail_quote">On Thu, Dec 11, 2014 at 9:32 AM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Justin,<br>
<br>
The current regression.sh code doesn't capture /var/log/messages which<br>
means whether the system ran out of memory or not can not be justified<br>
looking at the the log archive. I strongly believe we should capture<br>
this message as part of archiving the log.<br>
<br>
Would you be able to do this change and apply it in Rackspace?<br>
<br>
~Atin<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div>