On Wed, Apr 13, 2016 at 1:05 PM, David Caro <dcaro@redhat.com> wrote: =20
On 04/10 20:52, Yaniv Kaul wrote:
On Sun, Apr 10, 2016 at 6:06 PM, Eyal Edri <eedri@redhat.com> wrote:
test_logs/
This is an annoying change of behavior. In the past, I believe the lo= gs were under the deployment dir. Now, they are here. It requires cleani= ng them manually every time.
Before it also required manual cleanup every time, it just turned out, =
--M9pltayyoy9lWEMH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 04/13 13:35, Yaniv Kaul wrote: that
while doing the manual cleanup of the prefix (with ./run_suite -c) the = logs were removed too (that was also an issue on jenkins, as you had to extr= act the logs before the cleanup)
=20 1. Makes sense to me that you'll extract the logs before cleanup.
The collect command is the one extracting the logs, what we did before is extract them, into the same prefix (that's what I think it's wrong, the pre= fix is one thing, and the artifacts you collect are another)
2. It did not cause a re-run to fail, which now, unless you cleanup AND rm the files, it will. =20
It's part of issues we'll have to fix if we want (and I believe we do) support multiple execution.
=20 Yep. =20 =20
It supports multiple execution as long as you are not running the same suite, same as before, the issue here is that you are using a very specific fl=
ow
that is not used anywhere else, and thus, facing issues and user cases that noone else has. I really recommend: * Moving to the same flow jenkins uses * Moving jenkins to the same flow you use
=20 I'm running ./run_suite.sh -o /home/zram/3.6 basic_suite_3.6 and cleanup: lagocli --prefix-path /home/zram/3.6/current cleanup =20 over and over and over and over... =20 What should I be running?
=20
I consider it as a regression in a way, since it's a changed behavior=
rm -rf test_logs ./run_suite.sh basic_suite_3.6 ./run_suite.sh --cleanup basic_suite_3.6 That's the jenkins flow more or less, you could even run something closer by using: mock_runner.sh --execute-script automation/basic_suite_3.6.sh fc22 That is quite closer to what jenkins runs, that already takes care of the test_logs directory, moving it to exported-artifacts (where jenkins archives it) and removing it if it exists. Though you will not have any caching and zram execution (just as the jenkins slaves don't have it). -
and
I'm not sure for the better.
It changed behavior yes, and it improved the log collection and cleanup procedures on jenkins. To alleviate that issue, I sent a patch for that in the beginning of the lago project that was never merged, feel free to open a task for that too, should be relatively easy to implement some kind of log rotation if the destinati= on directory already exists.
Y.
_______________________________________________ lago-devel mailing list lago-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/lago-devel
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605 --M9pltayyoy9lWEMH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJXDidCAAoJEEBxx+HSYmnDpoQIAJvRW9IIMJkad/KOY37dw78g 6VWoIWDhARqe79n0/0Eaf5elhq2Ey813fi3myclmgcdOZbJ3XswY6ODt1P85I7ME cJTqQLpisB0Bn+07PxsgF8LONGRjt6k6IEFaBXIMYnpg5mlppA3p78zVXZscchAr 9LV5E/Wpk7H3osaoQ2fCj81eYBGxtMm8ZRodz1rlAKTemTRupnbL9bECWeFTU4KZ nSBqhDdcrC+ce2LazFiunShomSY+E7usd85WFihZr8QrfbSxEcSjOo0ypJEU6h6A ZrDE0UGDW8cCNucOHuxj6f7bUpXFkShZiZUpkT2lmQ+vOPctQq7/BZS8k1UqOKY= =ty+F -----END PGP SIGNATURE----- --M9pltayyoy9lWEMH--