<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 13, 2016 at 1:05 PM, David Caro <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 04/10 20:52, Yaniv Kaul wrote:<br>
> On Sun, Apr 10, 2016 at 6:06 PM, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
><br>
> > test_logs/<br>
><br>
><br>
> This is an annoying change of behavior. In the past, I believe the logs<br>
> were under the deployment dir. Now, they are here. It requires cleaning<br>
> them manually every time.<br>
<br>
</span>Before it also required manual cleanup every time, it just turned out, that<br>
while doing the manual cleanup of the prefix (with ./run_suite -c) the logs<br>
were removed too (that was also an issue on jenkins, as you had to extract the<br>
logs before the cleanup)<br></blockquote><div><br></div><div>1. Makes sense to me that you'll extract the logs before cleanup. </div><div>2. It did not cause a re-run to fail, which now, unless you cleanup AND rm the files, it will.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> It's part of issues we'll have to fix if we want (and I believe we do)<br>
> support multiple execution.<br></span></blockquote><div><br></div><div>Yep.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
</span>It supports multiple execution as long as you are not running the same suite,<br>
same as before, the issue here is that you are using a very specific flow that<br>
is not used anywhere else, and thus, facing issues and user cases that noone<br>
else has.<br>
I really recommend:<br>
* Moving to the same flow jenkins uses<br>
* Moving jenkins to the same flow you use<br></blockquote><div><br></div><div>I'm running ./run_suite.sh -o /home/zram/3.6 basic_suite_3.6 </div><div>and cleanup:</div><div>lagocli --prefix-path /home/zram/3.6/current cleanup</div><div><br></div><div>over and over and over and over...</div><div><br></div><div>What should I be running?</div><div>Y.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> I consider it as a regression in a way, since it's a changed behavior - and<br>
> I'm not sure for the better.<br>
<br>
</span>It changed behavior yes, and it improved the log collection and cleanup<br>
procedures on jenkins.<br>
To alleviate that issue, I sent a patch for that in the beginning of the lago<br>
project that was never merged, feel free to open a task for that too, should be<br>
relatively easy to implement some kind of log rotation if the destination<br>
directory already exists.<br>
<br>
> Y.<br>
<br>
> _______________________________________________<br>
> lago-devel mailing list<br>
> <a href="mailto:lago-devel@ovirt.org">lago-devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/lago-devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/lago-devel</a><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
David Caro<br>
<br>
Red Hat S.L.<br>
Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
<br>
Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605">+420 532 294 605</a><br>
Email: <a href="mailto:dcaro@redhat.com">dcaro@redhat.com</a><br>
IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
RHT Global #: 82-62605<br>
</font></span></blockquote></div><br></div></div>