20:00:04 #startmeeting Horizon 20:00:06 Meeting started Wed May 11 20:00:04 2016 UTC and is due to finish in 60 minutes. The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:10 The meeting name has been set to 'horizon' 20:00:24 o/ 20:00:34 robcresswell had other engagements so you're stuck with me 20:01:03 o/ 20:01:13 (◠‿◠✿)ノ 20:01:43 another large crowd ;) 20:02:02 o/ 20:02:20 and two look familiar from 12 hours ago 20:02:39 let's get started 20:02:57 The agenda for today can be found at 20:03:00 #link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-05-11_2000_UTC 20:03:17 there are a couple of notices 20:03:30 one the bug report is updated 20:03:38 #link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport 20:04:03 with some bugs and bps currently targeted 20:04:21 so take a look and prioritize appropriately 20:04:44 2nd notice is about the midcycle 20:04:56 a poll for dates is: 20:05:03 #link http://doodle.com/poll/xvchsbbs4qz9tzr7 20:05:29 if you plan on attending please vote with your availability 20:05:47 I'm not entirely sure the where 20:06:12 the where might dictate the ability to attend 20:06:21 right 20:06:30 it was not in the email to the ML either 20:06:35 just checked 20:06:56 #action robcresswell tells us where we're going for midcycle 20:06:56 robcreswell mentioned that it may be San Francisco 20:07:28 ok 20:07:52 that's it for notices and agenda 20:07:59 #topic Open Discussion 20:08:41 Does anyone know what's going on with the integration tests lately? 20:08:56 hopefully once https://review.openstack.org/#/c/315050/ is merged we should get much fewer failures 20:09:19 Great. Thanks, tsufiev. 20:09:30 but if it's not, here is an etherpad we're going to update to keep track of actual failures: https://etherpad.openstack.org/p/horizon-integration-tests-failures 20:09:41 I find it easier to use than kibana 20:10:03 categorize failures, see how frequent they are etc 20:10:03 ok, good to know. 20:10:14 tsufiev: what about elastic recheck? 20:10:19 current form is not final, may adjust it to our needs 20:11:16 david-lyle, what's the usual workflow with elastic recheck that may help us in navigating in different failures? 20:11:45 if you put those signatures in elastic recheck, you would get a count on the failure numbers and the notice when it fails on the patch in gerrit 20:11:47 I mean I'm not very familiar with ER facilities that really help finding out root causes... 20:12:10 and an entry on here http://status.openstack.org//elastic-recheck/ 20:12:25 okay, I'll try it :) 20:12:44 it's more about quantifying the failures and assess if they actually went away 20:13:15 just something for the future 20:13:43 thanks, I have to eventually get used to these big data helpers 20:14:02 my first impression with kibana wasn't very... friendly 20:14:14 the second thing to check is http://status.openstack.org//openstack-health/#/g/project/openstack~2Fhorizon?groupKey=project&resolutionKey=hour&end=2016-05-11T20:13:19.115Z 20:14:41 but for some reason the failures are not showing up for integration jobs 20:15:00 hehe 20:15:12 you see, the job is fine :) 20:15:13 so that might be worth checking into 20:15:25 kibana is a giant blobof js, I hear horizonay know how to workwith that >_> 20:16:12 it's all an illusion clarkb 20:16:31 being a developer doesn't mean we all know how to fix an electric kettle :) 20:16:35 kibana 3 is all client side and kibana 4 is node.js 20:16:48 from bad to worse 20:16:51 :) 20:16:57 lool 20:17:20 we currently run 3 20:17:29 so the integration job fix just merged 20:17:52 if you still encounter any failures in check job, just rebase your work onto latest master 20:18:03 tsufiev: was it only failing in check? 20:18:07 * tsufiev crosses fingers 20:18:16 that would explain health not showing failures 20:18:22 thanks tsufiev 20:18:22 but seems odd 20:18:50 david-lyle, AFAIK, gate job always runs against latest master, but check is run for topic branches which may not be up to date 20:19:09 no, failures were in both pipelines 20:19:17 ok, that makes more sense 20:19:27 your phrasing confused me 20:19:36 but I started in that direction ;) 20:19:41 yeah, I fancy being cryptic sometimes :) 20:20:21 since we don't have a blueprint for this, as blueprints don't really track CP stuff 20:20:30 I have created a tempest plugin for horizon 20:20:46 it's merged and there is a new test job that runs on check which isn't voting 20:20:47 btw, I've noticed that there were some tempest failures as well 20:21:12 cannot give a specific link though 20:21:28 I'm finalizing the job setup, once that's ready and passing, we can run that on gate as well 20:21:40 and remove our test from integrated tempest 20:22:05 then we can move forward with upper-constraints and new xstatic packages 20:22:22 david-lyle, or the thing you're speaking about is not related to dsvm-tempest job? 20:22:35 tsufiev: no 20:22:55 :o 20:22:59 well, gate-horizon-dsvm-tempest-plugin 20:23:01 job 20:23:33 is that what you're referring to? 20:24:01 the job isn't doing much yet, I have another patch up that I am testing out 20:24:27 https://review.openstack.org/#/c/314795/ 20:24:36 anyway, just a status report 20:24:42 I think yes 20:25:25 well, never mind, if it wasn't voting yet, then I most likely confused it with something else 20:25:32 as that thing was voting 20:25:48 ok 20:26:01 when you look into many failures, they start looking into you :/ 20:26:19 umm talking about failures and gate 20:26:45 did someone saw michael's email referring to npm mirrors? 20:26:47 http://lists.openstack.org/pipermail/openstack-dev/2016-May/094719.html 20:27:17 project I guess? 20:27:24 agh, cut phrase 20:27:38 now I did :) 20:27:39 we are supposed to add the nam mirrors to the project I guess 20:28:20 I tried it locally 20:28:31 could we just change npm job builders? 20:29:01 ahh, now I am reading it properly lmao 20:29:17 its just to test it locally and report any errors, nothing to do with touching the project 20:29:20 sorry for the noise 20:29:27 * itxaka retreats 20:31:22 any other items? 20:31:58 so we get to ignore all test jobs, then? great. let's move forward ;) 20:32:22 wat :)? 20:32:31 just trolling / kidding 20:32:31 * david-lyle thinks ducttape_ misread something 20:32:53 david-lyle what's the net result of all this? 20:33:04 TravT: this? 20:33:14 ^^^ 20:33:21 last 15 mins 20:33:38 status update 20:33:44 that there are a lot of test jobs failing / getting fixed. it's getting better very soon 20:33:53 integration tests should be working better 20:34:04 plans for xstatic upgrades moving forward 20:34:12 * TravT will send thank you card to david-lyle 20:34:48 there is an npm mirror that will reduce failures and fragility in npm dependent tests 20:35:26 one more reason to come by the end of meeting :) 20:36:30 any other items? 20:37:03 any hasty decisions to make? 20:37:10 going twice 20:37:34 * TravT sold 20:37:39 Have a banner week folks. Keep slinging that cloud. 20:37:43 #endmeeting