Tuesday, 2016-10-04

*** pvaneck has quit IRC00:01
*** markvoelker has joined #refstack00:29
*** markvoelker has quit IRC00:34
*** Rockyg has quit IRC00:44
*** markvoelker has joined #refstack00:54
*** clee has quit IRC05:10
*** clee has joined #refstack05:11
*** pilgrimstack has quit IRC06:50
*** pilgrimstack has joined #refstack06:53
*** markvoelker has quit IRC07:24
*** pilgrimstack1 has joined #refstack07:34
*** pilgrimstack has quit IRC07:34
*** pilgrimstack has joined #refstack07:57
*** pilgrimstack1 has quit IRC07:57
*** markvoelker has joined #refstack08:24
*** markvoelker has quit IRC08:29
*** markvoelker has joined #refstack10:26
*** markvoelker has quit IRC10:31
openstackgerritGhe Rivero proposed openstack/refstack-client: Fix regex to find test id  https://review.openstack.org/38123210:53
*** markvoelker has joined #refstack11:27
*** markvoelker has quit IRC11:32
*** edmondsw has joined #refstack12:18
*** markvoelker has joined #refstack12:33
*** pilgrimstack has quit IRC13:36
*** pilgrimstack1 has joined #refstack13:49
-openstackstatus- NOTICE: The Gerrit service on review.openstack.org is being restarted to address performance degradation and should return momentarily14:02
*** openstackgerrit has quit IRC16:26
*** openstackgerrit has joined #refstack16:28
*** openstackgerrit has quit IRC16:28
*** openstackgerrit has joined #refstack16:29
*** openstackgerrit has quit IRC16:30
*** openstackgerrit has joined #refstack16:31
*** selena_092 has joined #refstack17:22
selena_092hello, i have question related 2016.08 list of tests...is there a way to retrieve list of tests that are for newton release ? https://refstack.openstack.org/api/v1/guidelines/2016.08/17:23
selena_092its very confusing as to which tempest tag should be used for test because lot of tests im getting "not found in Tempest list."17:24
selena_092thats because tests name have been changing over the time and i guess this is refstack way of ensuring it covers a test for all tempest releases(i.e. its tags)17:25
hogepodgeselena_092: can you send us a list of the tests that have changed names?17:25
hogepodgeselena_092: we update the current guidelines with new and old test names, and refstack server and client use that to do the right thing17:26
selena_092for instance "tempest.api.network.test_networks.NetworksTestJSON.test_list_networks NOT FOUND " and thats because of this commit https://github.com/openstack/tempest/commit/e4184ea28e21b86edc28c9f3c02ec28d0d2fb476 , as a consequence if i want to run this i will have to use tempest tag prior to tag 6, however tag prior 12 is not even supported for n17:27
selena_092ewton17:27
selena_092hogepodge: sure17:27
hogepodgeselena_092: even just a paste will help, we can get a patch in pretty quickly17:28
selena_092hogepodge: thanks im on it..im pasting on paste.openstack.org one by one..thanks a lot for quick followup17:29
hogepodgeselena_092: you're the second person who has mentioned it today, I just want to get a patch in so folks aren't tripped up by it any more17:29
selena_092hogepodge: heres the list http://paste.openstack.org/show/584270/17:32
selena_092this was when i ran tempest master of yesterday with refstack and used the 2016.08 list of tests17:33
selena_092and my deployment was newton17:33
hogepodgeselena_092: thanks17:33
hogepodgeselena_092: line 13 was just fixed by this patch: https://review.openstack.org/#/c/373987/4 but the others need to be done too. I'll get on it.17:35
selena_092hogepodge: thanks so much..for passing the defcore criteria of 2016.08. i should retrieve list of tests like this ? https://refstack.openstack.org/api/v1/guidelines/2016.08/tests?target=platform&type=required&alias=true&flag=false17:37
hogepodgeselena_092: yeah17:38
*** pilgrimstack1 has quit IRC17:39
selena_092hogepodge: there is a new test i see tempest.api.volume.v2.test_volumes_list.VolumesV2ListTestJSON.test_volume_list_pagination[id-af55e775-8e4b-4feb-8719-215c43b0238c] thats now aded and also marked as required however i want to mention here this test fails with HTTPS based endpoints of cinder as i found in our environment , i raised a bug here htt17:40
selena_092ps://bugs.launchpad.net/bugs/1532116 for tempest team, they confirmed its because lack of  X-Forwarded-For HTTP header17:40
selena_092hogepodge: just to reconfirm, after the alias fix , refstack wont complain about "NOT FOUND" error for thoslist of tests ..right?17:45
hogepodgeselena_092: it will still complain. from what I understand refstack builds the list of tests to run and includes the aliases17:53
hogepodgeselena_092: so the one that doesn't exist will throw that error, but the one that does exist will still run and be reported appropriately17:53
hogepodgeselena_092: I'm looking through the list you provided and so far it looks like everything but the one I mentioned already has an alias associated with it17:54
hogepodgecatherineD: should be able to help you more on how it works17:54
selena_092hogepodge: so when submitting the 0.json in .testrepository of test results to refstack API, we  will not get failure of tests that had "NOT FOUND " ..17:54
selena_092catherineD: ^^17:55
hogepodgeselena_092: if the alias was run and passed, it should not be reported as failure17:55
selena_092hogepodge: ok that makes sense now..please let me know once you push a patch for alias of those lists of list  above :)17:56
selena_092hogepodge: what about https://bugs.launchpad.net/tempest/+bug/1532116 and its impact on  tempest.api.volume.v2.test_volumes_list.VolumesV2ListTestJSON.test_volume_list_pagination ? can you guys mark it flagged? this is a test that passes only if we have HTTP based endpoints but fails for HTTPS based cinder endpoints ..17:58
openstackLaunchpad bug 1532116 in tempest "Tempest volume v2 test_volume_list_pagination fails for https based endpoints" [Undecided,New] - Assigned to Daryl Walleck (dwalleck)17:58
hogepodgeselena_092: all of the tests have aliases18:12
*** pvaneck has joined #refstack18:13
hogepodgeselena_092: can you submit a flag patch to the defcore repository so we can discuss it during out next meeting (which happens tomorrow)18:13
*** pilgrimstack has joined #refstack18:13
selena_092hogepodge: thanks will do it.18:28
hogepodgeselena_092: thanks! flags always carry more weight when it's vendor reported and backed by a bug, so I don't think it will be a problem.18:40
*** Rockyg has joined #refstack18:43
selena_092hogepodge: can you please share your patch for the aliases of tests i reported ?18:49
selena_092or they aliases already ?18:49
selena_092lol i cannot search on review.openstack.org by owner:hogepodge :/18:52
openstackgerritMerged openstack/refstack: Fix typo: remove redundant 'the'  https://review.openstack.org/38093718:53
hogepodgeselena_092: user owner chris@openstack.org18:58
selena_092sorry i found it..i was looking if you merged any changes for aliases of those tests i reported to you..?18:59
openstackgerritMerged openstack/refstack-client: Fix missing dependency in refstack-client  https://review.openstack.org/36118919:51
catherineDluzC: ping19:54
luzCyes19:55
luzCmy understanding is that test cases in tempest have a idempotent_id which is unique...19:57
luzCher hand... while we use our implementation - docs are up to date)19:57
luzC<catherine_d|1> there is no doc update from our side because the implementation is a black box to RefStack users19:57
luzCups wrong copy paste19:57
luzChttp://docs.openstack.org/developer/tempest/HACKING.html#test-identification-with-idempotent-id19:57
catherineDsee this bug report about uniqueness of the idempotent_id https://bugs.launchpad.net/tempest/+bug/143370019:59
openstackLaunchpad bug 1433700 in tempest "Multiple test cases associated with same test UUID" [Undecided,Invalid] - Assigned to Sergey Slipushenko (sslypushenko)19:59
catherineDthis is reason why even today the guideline are still using fully qualified test name (with aliases) as the testcases name else a list of idempotent_id would ahve been easier20:00
luzCohhh20:02
luzCI see20:02
luzCthen current behavior is wrong...20:03
luzCfrom ostestr perspective, we still need to pass a whitelist which is a file containing a regex on each line...20:06
luzCsintaxis such as "tempest.api.test2[id-3,smoke]" won't work for ostestr... it will not find coincidences...20:08
luzCwe have to still create the withelist using the fully qualified test name such as "tempest.api.test2"20:09
*** pilgrimstack has quit IRC20:11
luzCam I making any sense?20:18
catherineDluzC:what is the format of the whitelist produces by ostestr ..20:19
catherineDselena_092: when retrieving testlist using this command https://refstack.openstack.org/api/v1/guidelines/2016.08/tests?target=platform&type=required&alias=true&flag=false20:21
selena_092catherineD: thanks..so even if refstack complains "test NOT FOUND" it wont effect as failure when submiitting to refstack API ..am i right?20:22
catherineDselena_092: this indicates that all aliases of a testcase will be returned. Of the list of aliases only one will match the testcase name of your current tempest version thus the rest will show not found20:23
catherineDcorrect20:23
catherineDbecause from refstack point of view we really do not knoiw which version the user is using20:23
selena_092catherineD: are you guys planning to release 2017.01 soon?20:24
selena_092thanks20:24
catherineDso they way I will do is to send the data up to refstack and concentrate on debug the failed list20:24
catherineDcan you locate the failed list on the web site?20:25
selena_092i havent submitted yet..just ran and saw that it was complaining about missing tests..20:25
catherineDI do not have the time line in mind .. usually the new guideline is 3 months lag of the OpenStack release20:26
selena_092catherineD: this is list of tests that refstack reported as MISSING when i ran latest tempest yesterday with refstack http://paste.openstack.org/show/584270/20:26
catherineDyea we should have document to descirbe that ... just do not have time yet20:26
luzC@CatherineD the format for whitelist is # Whitelist File20:27
luzC    ^regex1 # Include these tests20:27
luzC    .*regex2 # include those tests20:27
catherineDyup I have cheked that listI can say all have them have alias soi you should be find20:27
selena_092catherineD: thanks so much..20:28
catherineDselena_092: when you submit results pls submit result with signatiure ,... that way yiu can delete the result that you don't wnat and keep our system clean20:28
catherineDselena_092: are you a memeber of openstack?20:29
catherineDwe use openstack openid for authentication ... therefore you need to be an openstack member to login as a user at refstack20:29
selena_092catherineD: yes our team member already is20:30
selena_092and we submitted and got signed successfully for mitaka :)20:30
catherineDthen definitely upload the data with siganture20:30
catherineDselena_092: congrats !!!20:31
catherineDso you are all set?20:31
selena_092catherineD: yes , thank you so much for the help :)20:31
catherineDone of the thing we really would like the community to do is to test all API (of course after you test the small list of must pass test for ease of de bug ) that way it give us datato have a meaningful defined list for the next guideline like 2017.0120:33
catherineDluzC: then it is a bit difference then what refstack-client whitelist goal is then?20:34
catherineDseems like we still need refstack-own whitelist20:34
catherineDselena_092: yw20:35
luzC@catherineD ostestr and "tempest run" whitelist are regexes to run the test cases... refstack-client normalization creates a list that matches the names from the guideline to the actual existing names on the tempest installation...20:40
luzC@catherineD I'm going to dig more into the whitelist to fix it (stop using ids on the whitelist)... or try to reuse the full normalized TC list20:44
*** selena_092 has quit IRC20:44
*** pilgrimstack has joined #refstack20:59
*** pilgrimstack has quit IRC21:04
luzC@CatherineD i was taking a look at the bug again... I noticed that ids refer to the same test case, sometimes it uses available protocols or versions... at the end... valid TCs from the guideline should pass right?21:22
*** Rockyg has quit IRC21:55
catherineDluzC: pass fail checking is done strictly using fully qualified testcase (TC) name (with aliases) so if refstack shows test passed that means the TC name matched one of the aliases in the test list22:07
*** edmondsw has quit IRC22:10
luzCcatherineD I don't see the harm on running TCs via de id. Worst case scenario will be the same test case running for 2 versions: V1 and V2, even when only one is evaluated against the guideline...22:13
luzCI would recommend keeping the whitelist with idempotent ids...22:16
luzCthe other option would be to remove the whitelist and pass normalized list with "--load-list" which os-testr bypass directly to testr22:20

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!