09:01:20 <gmann> #startmeeting qa 09:01:21 <openstack> Meeting started Thu Oct 4 09:01:20 2018 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:01:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:24 <openstack> The meeting name has been set to 'qa' 09:01:51 <mbindlish> Hi 09:02:14 <gmann> mbindlish: hi 09:02:18 <gmann> who all here today 09:04:59 <gmann> mbindlish: seems two of us. 09:05:05 <mbindlish> yes 09:05:32 <gmann> do you have anything specific to discuss? otherwise i would like to cancel for today 09:06:01 <afazekas> o/ 09:06:02 <mbindlish> I want to know about bug triage 09:06:24 <gmann> afazekas: hi 09:06:39 <afazekas> gmann, hi 09:06:44 <gmann> ok let's start now, we have 3 peeple 09:07:46 <gmann> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 09:07:50 <gmann> today agenda ^^ 09:09:31 <gmann> #topic Announcement and Action Item (Optional) 09:09:50 <gmann> no announcement as such, checking AI 09:10:19 <gmann> no action item seems 09:10:29 <gmann> #topic Stein Priority Items progress 09:10:42 <gmann> #link https://etherpad.openstack.org/p/qa-stein-priority 09:11:20 <gmann> i have not tracked them yet. but if anyone have any update ? 09:11:29 <gmann> afazekas: your sshable patch is merged right ? 09:11:59 <afazekas> gmann, yesfor interface tests, but still need to deal with volumes 09:12:14 <gmann> ok 09:12:32 <gmann> thanks 09:12:57 <gmann> i will skip other item tracking for today. 09:12:58 <afazekas> Actually artom helped us with this change https://review.openstack.org/#/c/600046/ 09:13:15 <gmann> afazekas: cool, artom thanks for that 09:14:12 <gmann> #topic OpenStack Events Updates and Planning 09:14:43 <gmann> COMPLETED: Denver PTG 09:14:49 <gmann> this i need to remove now 09:14:56 <gmann> Next: Berlin Summit 09:15:07 <gmann> Forum Sessions Brainstorming 09:15:51 * afazekas still not does with Denver paper work, I'll check can I attend the Berlin event 09:16:19 <gmann> heh, paper work is painful 09:16:28 <gmann> hope to see you in berlin 09:16:35 <gmann> Forum Sessions Brainstorming 09:16:49 <afazekas> I hope I can show a demo of faster dev install that time 09:16:54 <gmann> i think forum sessions date is extended but not sure till when 09:17:01 <gmann> afazekas: perfect 09:18:10 <gmann> but i have proposed QA feedback sessions 09:18:30 <gmann> #topic Sub Teams highlights 09:19:38 <gmann> Tempest 09:19:51 <gmann> #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 09:19:57 <gmann> these are the open review. 09:20:21 <gmann> anythings specific to discuss about tempest 09:21:26 <mbindlish> I am fearing that multiple patches ZUUL is failing due to this condition: 09:21:26 <mbindlish> https://github.com/openstack/tempest/blob/master/tempest/tests/cmd/test_verify_tempest_config.py#L591 09:21:51 <mbindlish> I will debug the root cause for it 09:22:13 <gmann> mbindlish: is it? any link or bug ? 09:22:32 <mbindlish> not any bug/link....but most of patches i have checked 09:22:49 <mbindlish> they have py27 or py36 fail due to this condition 09:23:07 <gmann> mbindlish: yeah, patch failure link 09:24:37 <mbindlish> gmann: http://logs.openstack.org/32/582832/5/check/openstack-tox-py35/a86a291/testr_results.html.gz 09:25:15 <afazekas> 'ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/zuul/src/git.openstack.org/openstack/tempest/etc/tempest.conf.sample' mode='w' encoding='UTF-8'> 09:25:15 <afazekas> generate(conf)' 09:25:31 <afazekas> Maybe we just need to close it explicitly .. 09:25:51 <mbindlish> @gmann another one: https://review.openstack.org/#/c/577730/ 09:26:29 <afazekas> Read the warning in the test case failure 09:27:14 <mbindlish> afazekas: yes 09:27:59 <gmann> yeah i think we should do that 09:28:14 <mbindlish> but why not py27 failed 09:29:23 <afazekas> WILD guess: maybe py3 has some lazy file create tactic .. 09:29:51 <gmann> but it is not occurring always 09:30:31 <mbindlish> yes, also i checked in my local env..it was running fine there 09:31:48 <gmann> mbindlish: can u log bug and try it closling it explicitly 09:31:53 <afazekas> anyway explicit closing considered as good practice, we will see does it helps . 09:31:59 <gmann> yea 09:32:02 <mbindlish> gmann: sure 09:32:12 <gmann> mbindlish: thanks for monitoring that. 09:32:18 <mbindlish> :) 09:32:43 <gmann> Patrole agenda needs to be updated with latest items we disucssed in PTG 09:33:01 <gmann> let's move to bug 09:33:08 <gmann> #topic Bug Triage 09:33:38 <gmann> chandan informed he will not be present today due ot PyCon india 09:33:47 <gmann> mbindlish: next week is your turn. 09:33:58 <mbindlish> gmann: yes 09:34:29 <mbindlish> i need your guidance over it 09:34:41 <gmann> what i am expecting is 1. you keep traiging/add comment on 'new' bugs till next office hour 09:35:07 <gmann> guide for bug triage - #link https://wiki.openstack.org/wiki/BugTriage 09:35:42 <mbindlish> gmann: ok, will check it 09:35:50 <gmann> 2. make report of progress and note down the key bugs which we need to discussed/triage together in office hour (i will tell the report way) 09:36:13 <mbindlish> fine 09:36:32 <gmann> mbindlish: thanks, feel free to ask any query on that anytime on channel 09:36:53 <mbindlish> gmann: thanks for your support :) 09:37:42 <gmann> we have high number for 'new' bugs now which we need to get down to minimum or 0 09:37:52 <mbindlish> :+1 09:37:56 <gmann> #topic Open Discussion 09:38:06 <gmann> anything else to discuss ? 09:38:43 <gmann> ok, if nothing else let's close it 09:38:49 <gmann> afazekas|appoint: mbindlish thanks for joining 09:38:53 <gmann> #endmeeting