15:00:08 <vishalmanchanda> #startmeeting horizon 15:00:09 <opendevmeet> Meeting started Wed Mar 30 15:00:08 2022 UTC and is due to finish in 60 minutes. The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:09 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:09 <opendevmeet> The meeting name has been set to 'horizon' 15:00:33 <tmazur> o/ 15:00:48 <vishalmanchanda> Hello everyone 15:00:50 <rdopiera> o/~ 15:00:58 <amotoki> hi 15:01:37 <vishalmanchanda> e0ne: ping for horizon weekly meeting. 15:01:44 <vishalmanchanda> ok Let's start 15:01:58 <vishalmanchanda> #topic Notices 15:02:25 <vishalmanchanda> few announcement for this week. 15:03:04 <vishalmanchanda> Today release team will cut the final release for Yoga Cycle and share the same on open-discuss ML. 15:03:18 <vishalmanchanda> Thanks Everyone for your contributions in the Yoga Cycle. 15:03:47 <vishalmanchanda> cheers:) 15:04:08 <vishalmanchanda> Next week is PTG week. 15:04:36 <vishalmanchanda> So there will be no weekly meeting next week. 15:04:58 <vishalmanchanda> #link https://etherpad.opendev.org/p/horizon-zed-ptg 15:05:46 <vishalmanchanda> I have added time Slots for all the topics, please take a look and let me know if you want to join any topic discussion and allotted time doesn't work for you. 15:06:35 <vishalmanchanda> I will try to move it to other available slots or you can add your thoughts about that topic on etherpad and I can discuss those points on your behalf. 15:07:13 <vishalmanchanda> Also, please add your name on the Zed PTG etherpad, so at least I know you are going to attend the PTG 15:07:30 <vishalmanchanda> So I can ping you when we start the discussion. 15:08:45 <vishalmanchanda> On Monday, April 4 we have PTL+TC interaction, you can also join. 15:08:59 <vishalmanchanda> More details you can find on etherpad. 15:10:11 <vishalmanchanda> Also, don't hesitate to add any topics which you want to raise in the PTG etherpad. 15:10:29 <vishalmanchanda> moving to next announcement 15:11:13 <vishalmanchanda> I cut a new release of the horizon for stable/yoga branch to include the Keystone admin endpoint and Hide System Scope Menu patch. 15:11:23 <vishalmanchanda> #link https://review.opendev.org/c/openstack/releases/+/835461 15:11:56 <vishalmanchanda> that's all announcements from my side for this week. 15:12:21 <vishalmanchanda> If anyone has any announcements to make, please go ahead. 15:14:27 <vishalmanchanda> There is no topic added for disscusion to our agenda etherpad https://etherpad.opendev.org/p/horizon-release-priorities (at Line 32) 15:14:48 <vishalmanchanda> #topic open-discussion 15:15:25 <vishalmanchanda> Does anyone wants to discuss any topic, please go ahead. 15:16:23 <tmazur> I wanted to discuss the patch on integration tests 15:16:25 <tmazur> https://review.opendev.org/c/openstack/horizon/+/819725 15:16:57 <tmazur> It seems that tests failures are consistent, it's always time out 15:17:25 <tmazur> And it's kinda logical, since the patch adds a bunch of new tests 15:17:58 <tmazur> So the question is: should we increase the time limit? And if yes, then how to do that? 15:19:35 <vishalmanchanda> I have no idea about it, I will check and share with you if found something. 15:19:56 <tmazur> vishalmanchanda: thanks! 15:20:28 <vishalmanchanda> maybe e0ne knows more about the time limit. 15:21:18 <amotoki> the job timeout can be set in zuul.yaml 15:21:57 <amotoki> I am not sure what causes the timeout but at least it sounds good to try to increate the timeout and see what changes. 15:22:40 <vishalmanchanda> amotoki: you mean here https://github.com/openstack/horizon/blob/master/.zuul.d/tempest-and-integrated.yaml#L2 15:22:52 <vishalmanchanda> we can increase the time limit. 15:22:57 <amotoki> vishalmanchanda: yes 15:23:30 <amotoki> setting timeout to a bigger value means we need to wait more and more unfortunately :p 15:23:44 <vishalmanchanda> amotoki: ok, thanks I will also investigate that. 15:24:15 <amotoki> for example, https://opendev.org/openstack/neutron/src/branch/master/zuul.d/base.yaml#L5 15:25:32 <vishalmanchanda> I don't see any issue with waiting for more time if jobs pass in the first attempt because in other OpenStack projects there are many jobs that take too much to run. 15:26:15 <amotoki> ideally it is better to explore a way to run the integration tests in parallel. 15:27:38 <tmazur> https://github.com/openstack/horizon/blob/master/.zuul.d/tempest-and-integrated.yaml 15:27:51 <vishalmanchanda> yeah good point. 15:29:07 <vishalmanchanda> tmazur: ok let's explore both options increase the time limit and run these tests in parallel. 15:29:26 <vishalmanchanda> I will also help you with that. 15:29:36 <tmazur> Yeah, I will tweak the time limit in my patch and we'll see how it goes 15:29:43 <vishalmanchanda> cool 15:30:25 <amotoki> I think the first step is to increase the timeout and see what changes. 15:30:42 <amotoki> running the tests in parallel would be the next step. 15:30:55 <vishalmanchanda> +1. 15:32:20 <vishalmanchanda> ok if nothing more to discuss, let's end this meeting. 15:32:46 <vishalmanchanda> Thanks everyone for joining, See you at the PTG. 15:32:59 <tmazur> Thanks everyone! 15:33:07 <vishalmanchanda> #endmeeting