<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 19, 2016 at 5:20 PM, Pranith Kumar Karampuri <span dir="ltr"><<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Result: PASS<br>
Build timed out (after 300 minutes). Marking the build as failed.<br>
Build was aborted<br>
Finished: FAILURE<br>
<br>
<a href="https://build.gluster.org/job/rackspace-regression-2GB-triggered/17664/console" rel="noreferrer" target="_blank">https://build.gluster.org/job/rackspace-regression-2GB-triggered/17664/console</a><span class="HOEnZb"><font color="#888888"><br>
<br>
Pranith<br></font></span></blockquote><div><br></div><div>This is due to build timeout. I had set it to 300 minute (5 hours).</div><div>Recently though, some patch has caused a major performance regression.</div><div>Tests which used to pass in 120 seconds are taking more than 200.</div><div>This has increased test run time from 200 minutes to greater than 300.</div><div><br></div><div>I have increased timeout value to 500 minutes now and it should not get aborted.</div><div><br></div><div>Someone really needs to look into the regression though. Pick any test from the console output above and run a .t file that took over 200000 ms.</div><div><br></div><div>Thanks,</div><div>Raghavendra </div></div><br></div></div>