Tuesday, 2021-01-12

*** tosky has quit IRC00:15
*** rcernin_ has quit IRC03:14
*** rcernin_ has joined #openstack-rally04:25
*** rcernin_ has quit IRC04:25
*** rcernin has joined #openstack-rally04:25
*** rcernin has quit IRC06:26
*** rcernin has joined #openstack-rally06:26
*** rcernin has quit IRC07:07
*** nikparasyr has joined #openstack-rally07:27
*** dave-mccowan has quit IRC07:30
*** tosky has joined #openstack-rally08:22
*** marosg has joined #openstack-rally11:21
marosgHi all. What happened to this project? Last commit is from Nov 2nd and I don't see andrey here. Is this still alive?11:27
*** andreykurilin has joined #openstack-rally13:35
marosghi andreykurilin ! I asked this two hours ago "Hi all. What happened to this project? Last commit is from Nov 2nd and I don't see andrey here. Is this still alive?"13:53
andreykurilinheh. I just saw your message at linkedin and start answering you there13:54
marosg:D13:54
andreykurilinso yes, project is alive13:54
andreykurilinI forgot to start IRC client at some point13:54
andreykurilinanyway, there was no much messages here :)13:54
marosgI wanted to ask - I see when my tempest fails some tests, rally still returns code 0, it is returning 1 only if it is not able to setup environment. Is that on purpose?13:56
andreykurilinoh...let me try to remember13:57
andreykurilinI do not have a better answer than "it is done in such way just by historical issues" and can not find a reasonable explanation why it was implemented in such way :)14:00
marosgwell, that is one the most common reasons everywhere. Thanks for update.14:02
andreykurilinMaybe, I was thinking that if we succeeded to execute a tool (verifier), rally made its work and and we should not fail14:02
andreykurilinbut now it sounds unreasonable and I'm ok about changing this behavior14:03
marosgas far as I understand the code, rally shoudl check return code from tempest and return it. I did not check if tempest is returning different code depending on results14:06
andreykurilinIt is not how it works.14:10
andreykurilinRally ignores the tempest CLI , we are consider tempest as like a subset of tests that should be executed via testr/stestr. Triggering testr/stestr with proper argument gives subunit output that rally parses in real-time14:12
andreykurilinthis gives the final dict with total and detailed numbers14:12
andreykurilinthis dict has all that is needed for returning the correct exit code14:13
andreykurilinthe proper exit code should be selected right after https://github.com/openstack/rally/blob/master/rally/cli/commands/verify.py#L527 based on results["totals"]14:14
marosgyes, that is the code I was looking at, that is where it returns 1 when env cannot be set and nothing after the test. And there I had no idea how is tempest really invoked14:17
andreykurilinit is invoked via run method of https://github.com/openstack/rally/blob/master/rally/plugins/verification/testr.py#L9014:19
andreykurilinthe exact command is produced by https://github.com/openstack/rally/blob/master/rally/plugins/verification/testr.py#L4314:20
andreykurilin^ It is for the case if you want to know more details:)14:20
andreykurilinActually, the whole logic is implemented in 2 repos (rally repo includes unified things that can be theoretically be re-used and rally-openstack includes tempest specific stuff) :)14:23
*** marosg has quit IRC18:05
*** nikparasyr has left #openstack-rally18:13
*** rcernin has joined #openstack-rally23:02

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!