18:59:17 #startmeeting infra 18:59:17 Meeting started Tue Apr 29 18:59:17 2014 UTC and is due to finish in 60 minutes. The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:59:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:59:20 The meeting name has been set to 'infra' 18:59:23 Agenda: 18:59:23 #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting 18:59:23 Last meeting: 18:59:23 #link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-04-22-19.01.html 18:59:39 #topic Gerrit upgrade 18:59:42 o/ ping if you need me otherwise I'm in -> -alt 19:00:07 heyo 19:00:17 we're early? 19:00:25 hi 19:00:26 i think this is the only thing we really have on the agenda... 19:00:28 fungi: are we? 19:00:33 not any more :) 19:00:46 heh 19:01:00 so, we upgraded! 19:01:05 yay! 19:01:10 i have a few things on the punch list 19:01:15 \o/ 19:01:18 * something's weird with tag jobs 19:01:30 o/ 19:01:48 * turbo hipster's vote looks wrong on this patch: https://review.openstack.org/#/c/86443/ 19:02:07 * and of course we need to restart for the cosmetic changes 19:02:16 that's all i have right now; am i missing anything? 19:02:17 yeah 19:02:23 it was re restart ;) 19:02:34 searching for strings doesn't seem to work 19:02:38 regex's work 19:02:43 jeblair, and "recheck migrations" did not work on that same review 19:02:53 i'm as of yet unconvinced turbo-hipster is operable. it ignored dims's recheck 19:02:57 that 19:03:17 yeah, i'm not really concerned about that. turbo-hipster inc has their own crack team of ops to deal with that... 19:03:19 jeblair: I noticed merge collision not -2ing a patch 19:03:21 they probably need a regex update 19:03:30 clarkb: hey 19:03:37 clarkb: you are on holidays 19:03:44 clarkb: heh, you're terrible at vacations 19:03:49 sdague: link? 19:04:00 let me go dig it up 19:04:12 https://review.openstack.org/#/c/44714/ 19:04:14 (re turbo-hipster -- it's the fact that it was -1 then +1 but the approval summary still said -1 that's troubling) 19:04:36 agreed 19:04:39 oh good grief, what's the deal with the bird? 19:04:49 not really here >_> 19:04:56 we should get rid of that 19:05:08 anteaya: what do you mean about searching for strings? 19:05:21 hah, I totally missed the bird when I looked at it this morning 19:05:37 I noticed that change because it was in my review list as 'submitted' 19:05:43 well, turbo-hipster +1'd patch 21 after -1'ing patch 23, so the -1 is accurate 19:05:51 zaro: if you look at teh backscroll with tjones and myself today, she was looking for message:"spawn refactor - phase 1" to return results 19:05:55 jesusaurus: good eye 19:05:56 it didn't 19:06:06 "Submitted, Merge Pending" that is 19:06:34 re gerrit upgrage : is it a known issue that the regex matching for jenkins results isn't doing the formatting any more? 19:06:34 sdague: oh, that's actually a missing dependency, not a conflict -- that's something we should fix in zuul 19:06:43 zaro: I got her going again with topic:^bp/vmware-spawn.* but taht doesn't solve the string search issue 19:06:44 ok 19:06:46 sdague: but i think it's consistent with old behavior 19:06:48 jeblair: i think jesusaurus's insight explains the turbo-hipster -1 rather well 19:07:11 fungi, jesusaurus: thanks for catching that; i'm striking it from the punch list 19:07:11 anteaya: hmm, i remember that working for me. 19:07:11 ianw: what regex? 19:07:14 ok, then it can wait until later 19:07:52 also, wow that change was started a long time ago. :) 19:07:59 ianw: the formatting is what we've got a pending fix merged for, awaiting the next reasonable timme to restart gerrit 19:08:22 fungi: would that explain my outcome with tjones? 19:08:33 yep 19:08:36 fungi: ok, thanks 19:08:39 anteaya: unrelated 19:08:49 hmmmm 19:09:02 jeblair: so question on dashboards, where do those go? (i.e. how do I submit them) 19:09:11 anteaya: i think ianw was asking about the regular expressions used in commentlink configuration within gerrit, not having to do with search queries 19:09:25 oh 19:10:22 sdague: i think mordred was looking into how to do that. they are special branches in the repo -- my guess is we might want to have jeepyb do it, or we might want to set up those branches for review. 19:10:28 anteaya: yeah, the regex's in https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/manifests/gerrit.pp 19:10:55 sdague: i think in the interim, we can manually push some in when you're ready 19:10:56 anteaya: i don't think the spaces work, you need to do "message:spawn message:refactor message:phase .." 19:10:57 jeblair: ok. I can probably convert most of these custom queries to dashboards, but having a way to review / test them would be good 19:11:25 zaro: yeah, which is not how I would expect to have to do a string search query 19:11:35 jeblair: ok, I'll see about converting the basic no negative feedback one, that will be the most generic one people will want I think 19:11:53 anteaya: gerrit doc doesn't say it supports what you want :) 19:11:55 zaro: searching for one word at a time and chaining them with AND worked but was contrary to my expectations 19:12:10 zaro: you used to be able to search for strings like that 19:12:10 sdague: yeah, we certainly want to review them; testing them might be hard without just pushing them in to see what happens. though the query language being the same as searches helps. 19:12:25 and I can't search for message:- or message:"-" 19:12:36 which was a character in the original string 19:13:14 interesting, i guess i never tried to search like that before. 19:13:35 jeblair: yeh 19:13:51 any other new-gerrit issues? 19:14:07 anteaya: my guess is secondary indexes are doing stop words, so that's dropped 19:14:16 it's a lucene index on the secondary, right? 19:14:25 sdague: yes 19:14:39 links including target="_blank" by default could be considered a new gerrit issue i suppose, though not sure whether it's one we care enough to solve/investigate 19:14:50 yeh, so think less "grep" and more google 19:15:34 fungi: i wonder if there's an option for that 19:16:09 i don't see a personal preferences option anyway 19:16:35 could be a global setting somewhere, i suppose 19:16:44 i'll dig in the config ref a little 19:17:43 we _could_ write a commentlink parser that strips them out 19:18:20 (which, i believe technically we have inadvertently done for the zuul links -- it's just inconsistent now) 19:18:36 (or will be after the restart) 19:18:53 true 19:19:10 apparently commentlinks are now configurable per-project as well 19:20:09 jeblair: I think this is a reasonable inbox zero kind of query - status:open NOT label:Code-Review>=0,self label:Verified>=1,jenkins NOT label:Code-Review<=-1 NOT label:Workflow<=-1 19:20:58 * sdague <3 queries that can mix label and id 19:21:08 yeah that's nice 19:21:32 sdague: what if you -2 a change? 19:21:58 label:Code-Review<=-1 would include -2 19:22:10 derp 19:22:17 :) 19:23:27 I think my only question is if NOT label:Code-Review>=0,self applies to all patches, or current patch only. If #1, then it probably has to change to >=1 19:23:29 my connection had dropped 19:23:36 what are stop words? 19:23:38 if #2 then it's probably ok 19:24:16 i believe labels only ever apply to the latest patchset 19:24:22 sdague: i would guess #2 based on my usage... 19:24:22 fungi: ok, cool 19:24:38 yeh, I'm trying to find an instance where I have an old 0 comment 19:26:45 #topic Upcoming project renames 19:26:53 we have some now 19:27:04 #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_project_renames 19:27:58 i have some things to do friday and will be out next week 19:28:07 ahh, i missed blazar was finally okayed. awesome 19:28:10 so i may not be particularly useful in that department for a bit 19:29:00 we could just do it on, say, thursday -- or we can see if the crew that's around next week is interested 19:29:31 i could rename things this weekend, but with both you and clarkb travelling that seems unwise. thursday's fine with me though, or roping people into it next week 19:29:52 i have no real preference and can do it whenever 19:30:26 fungi: i lean toward deferring it right now, we have quite a bit on our plate while being short-staffed 19:31:03 (i think i'm not eager to make _more_ work for us right now) 19:31:19 fair enough 19:31:42 it being the first 2.8 rename, we could have... surprises. 19:31:45 i'll bring it up next thursday and see how those who are around feel about viability 19:31:58 er, next tuesday (in the meeting) 19:32:05 *nod* 19:32:23 can you create a test repo and rename it prior to next tuesday 19:32:30 would that have any value? 19:32:53 guess not, since you can never delete anything in gerrit 19:32:57 anteaya: on review-dev, sure, if we have time. 19:33:05 oh okay, yeah there 19:33:42 #topic open discussion 19:33:56 anything else? 19:34:01 just wanted to chase up on https://review.openstack.org/#/c/86842/ 19:35:09 zaro: you were going to change the db schema on review-dev to match the db schema on review, were you not? 19:35:25 ianw: i'm cool with merging that later today, after i confirm i have no other gotchas in nodepool 19:35:40 fungi, ianw: ++ 19:36:25 thanks 19:37:35 well, thanks everyone, and enjoy the rest of the "off week" :) 19:37:40 #endmeeting