17:01:28 #startmeeting third-party 17:01:28 Meeting started Tue Apr 5 17:01:28 2016 UTC and is due to finish in 60 minutes. The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:32 The meeting name has been set to 'third_party' 17:02:14 ola 17:02:24 ja3: hey 17:02:41 morning/afternoon sir 17:02:55 who else is here for third-party CI working group meeting? 17:03:32 hi 17:04:20 hi asselin_ , sorry to hear that you have conflict with the meeting 17:04:25 #topic Announcements 17:04:45 Gerrit IP change is still happening on April 11 17:04:47 Gerrit IP Change: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088985.html 17:06:03 #topic CI Watch 17:07:17 Unit tests are slow-going. I did not push anything for review there. Currently working on getting some fixtures for gerrit event stream added 17:07:55 i.e. it is now possible to run a test with fake gerrit listener 17:08:39 the problem is that current test would have to directly examine resulting records in database, which is marginally useful 17:09:23 any questions? 17:09:56 #topic Common-CI Solution 17:10:09 asselin_: anything to discuss here? 17:10:25 no updates from me 17:10:29 I did not see many patches come in recently 17:10:42 ok, moving on :) 17:10:54 #topic Open Discussion 17:12:31 asselin_: would you like me to chair for you while you have the conflict? 17:12:42 mmedvede, yes, that would be great 17:13:40 asselin_: ok, would do 17:13:44 thank you 17:13:55 we've started to trigger our CI off of nova now, running full tempest instead of only smoke. still not ready to vote, tuning slave build times and such. 17:14:19 ...and my log server request is still going nowhere. 17:14:50 ja3: that is unfortunate 17:15:39 ja3: how long does your current test take? 17:15:51 well it's "lack of attention" nowhere, rather than "request denied" nowhere, so it could turn on a dime 17:16:33 they're getting close to on-par with upstream. bob has been seriously flogging it. 17:18:44 what matters to be able to report/vote is test reliability and stability. Initially you can ask for non-voting commenting permissions to validate how reliable your CI is 17:20:13 true, but we don't actually need any permissions to compare our results against upstream. 17:20:38 ja3: so once you get your logserver, you should be able to start commenting non-voting 17:20:58 assuming we're stable enough, yes 17:21:02 ja3: right, but if your CI is invisible, it is harder to collect stats 17:21:58 is anyone interested in collecting stats on our CI, when we don't think it's stable/reliable yet? I would not think so, but I'm willing to be wrong if there's some larger context I'm not grokking. 17:22:36 I'd think making it visible is basically just generating spam for onlookers, and I consider that impolite. 17:23:08 ...that's my current thinking at least. If I'm dragging knuckles w/o good reason, slap me around. 17:23:19 agree, it needs to be reasonably not broken :) 17:25:03 ja3: also if you follow the guidelines at 17:25:34 #link Third Party Testing http://docs.openstack.org/infra/system-config/third_party.html 17:26:06 one step is to add your account to gerrit group that should prevent spam emails 17:28:21 ok, any more topics? 17:30:06 thanks for attending 17:30:20 #endmeeting