Wednesday, 2017-05-17

jlkwell that's interesting00:15
jlkone of the "variants" is a job itself, the other is a list of the job itself00:15
jlkI've been messed up all this time because my docker deploy is using my github-v3 branch, which hasn't been rebased in a while. But the feature branch has some changes on it that maybe fix this problem.01:06
*** harlowja has quit IRC01:08
mordredjlk: well - hopefully the days of you being on a long-term branch are coming to a close01:08
jlkI've seriously messed up my mac, it thinks I'm user 501, which doesn't actually match my user name01:10
jlktime for a reboot!01:10
jlkit's been 30 days, I guess that's okay01:10
jlk10~ split terminal windows with 10+ vim processes in each. I'm sure I'll remember what I was doing01:11
mordredjlk: oh totaly. no context will be lost at all!01:14
*** dkranz_ has quit IRC01:39
jlkWell, the good news is that after fully rebasing, the problem persists.01:41
leifmadsengood news everyone!01:41
jlkI need to like tag a data object and get an pdb point every time that data object has something added to it02:46
leifmadsenmordred: ugh, my laptop locked up, and my znc didn't have enough scroll back (or the right kind of scroll back / history) for all the links you posted earlier. If you still have that blob of data, would you mind pastebin'ing it? (or anyone else)03:03
jlkOoooh I think I found it03:32
*** auggy has left #zuul03:40
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Extend job list when inheriting jobs  https://review.openstack.org/46539304:04
jlkmordred: jeblair not sure if you want a test for ^^04:05
*** harlowja has joined #zuul04:33
jlkDoes nodepool v3 use mysql any more?04:42
jlklooks like no04:43
tobiashjlk: mysql is gone with v3 :)05:01
jlkhuzahh05:01
SpamapS(except when you want the sql reporter ;)05:02
jlkyeah05:02
tobiashSpamapS: isn't that part of zuul?05:02
jlkdon't need that for what I'm tossing together05:02
SpamapSit is, just pointing out mysql moved from nodepool to zuul :)05:03
jlkwhich is funny, because in our v2.5 deployment, we were running mysql on the zuul node, instead of on the nodepool node05:04
tobiashso things are moving towards the right place05:05
jlkbut for v3 we may not use the sql reporter05:06
SpamapSjlk: I could see it being useful for building a webapp kind of like the openstack health dashboard.05:07
SpamapSbut otherwise probably not05:07
jlkfair05:07
jlkhttps://github.com/j2sol/z8s  zuul v3 mostly running in containers. I say mostly because it's the nodepool part that needs more work.05:49
jlkI could use some help getting this to work without nodepool, if possible.05:49
SpamapSNEAT05:50
* SpamapS was just reading it05:50
SpamapSjlk: I'm guessing dib + docker == fail?05:50
SpamapSthough not sure how it would fail05:51
SpamapSjust guessing05:51
jlkhaven't really got it to the point where it's trying to dib anything. I hvaen't defined any images yet05:52
jlkbut the zuul side will respond to webhooks shoved at it, will clone the repo in question, and try to fire off my noop job05:53
*** harlowja has quit IRC05:54
* jlk out05:55
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Add SSH Agent Primitives and usage  https://review.openstack.org/46271206:08
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Add support for bwrap  https://review.openstack.org/45385106:08
tobiashjlk: what are the problems with nodepool?06:18
tobiashI have currently everything running in docker06:18
tobiash(including nodepool-builder with dib)06:20
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Fix passing labels to Gerrit when they are not defined in All-Projects  https://review.openstack.org/46542006:35
*** DangerousDaren has joined #zuul06:36
*** mgagne has quit IRC06:53
*** mgagne has joined #zuul06:56
*** mgagne is now known as Guest2410306:56
*** bstinson has quit IRC06:58
*** bstinson has joined #zuul06:58
*** bhavik1 has joined #zuul07:08
*** bhavik1 has quit IRC07:52
*** isaacb has joined #zuul08:22
*** isaacb has quit IRC09:16
*** isaacb has joined #zuul09:25
*** Cibo_ has joined #zuul10:01
*** Cibo_ has quit IRC10:18
*** Cibo_ has joined #zuul10:27
*** jkilpatr has quit IRC10:38
*** Cibo_ has quit IRC10:48
*** jkilpatr has joined #zuul11:00
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: sql-reporter: add support for Ref change  https://review.openstack.org/46553912:38
tristanCSpamapS: Greeting sir, I'm actually trying to get a Jenkins-like dashboard for zuul jobs and found an issue with the sql reporter when used in the post pipeline... would you mind checking https://review.openstack.org/465539 ?12:48
mordredtristanC: +2 from me13:07
mordredShrews: I +2d the stack at https://review.openstack.org/#/q/topic:py3-nodepool - which should also pass tests now with your test fixes13:07
Shrewsmordred: ok. still battling some sort of illness, but will try to find some energy to look soon13:33
mordredShrews: no worries/rush13:35
mordredShrews: go be un-sick13:35
*** dkranz_ has joined #zuul13:36
leifmadsenwoah, a Jenkins like dashboard for Zuul?13:46
leifmadsentell me more!13:46
*** Cibo_ has joined #zuul13:59
Shrewspabelanger: mordred: the nodepool py3 changes lgtm except for https://review.openstack.org/46359414:18
*** rcarrillocruz has quit IRC14:20
Shrewspabelanger: i think https://pythonhosted.org/six/#six.reraise will work there14:20
*** Cibo_ has quit IRC14:26
*** Guest24103 is now known as mgagne14:32
*** mgagne has quit IRC14:32
*** mgagne has joined #zuul14:32
jlktobiash: no problems yet per se, I haven't tried to get it to build images yet. I was hoping I could have zuul execute noop job without needing a node, thus nodepool, but that wasn't working right.14:39
jlktobiash: do you have your docker files and docker-compose files anywhere public?14:40
clarkbjlk the zuul 'noop' job should be a special case that just returns a successful status without executing remotely14:43
jlkclarkb: I totally agree with that statement!14:45
jlkhowever my zuul install does not.14:45
clarkbI mean that is how it is implemented. at least for v2.514:45
jlklet me bring up the stack and stuff an event into it14:46
jlk(this is really useful to have it all dockerized14:46
jlk)14:46
jlkzuul-scheduler       | DEBUG:zuul.IndependentPipelineManager:Adding node request <NodeRequest 100-0000000000 <NodeSet OrderedDict()>> for job noop to item <QueueItem 0x7f70044f8cd0 for <Change 0x7f7004487a10 1,bb71d444ce36ea561bf98d83d05d2ccefe38525a> in check>14:47
jlkand then it sits there, because it doesn't get a node14:47
pabelangerShrews: I'll fix shortly14:48
*** isaacb has quit IRC16:00
*** DangerousDaren has quit IRC16:07
jeblairSpamapS, jlk: (from yesterday scrollback): at this point you can theoretically not run a zuul-merger (because zuul-executor implements the same functions), and i was going to remove it, however, due to the large amount of git repo operations related to configuration, i think it's best to keep it around because we may end up wanting to scale it separately from executors.16:09
jlkjeblair: I did notice that there is one function I don't think the executor does, which is the merger:update function.16:11
jlkjeblair: if we have a merger, it's doing information gathering things, right, it's not preparing trees for use in other places? It doesn't need any ports exposed or anything?16:12
jeblairmordred, jlk: there's some WIP documentation on job variants in https://review.openstack.org/46332816:13
jeblairjlk: yeah, merger:update is no longer needed (it means make sure the git repo for this project is up to date on this merger so that a post job can clone from this merger and get the right stuff.  that doesn't happen in v3 any more.)16:17
jeblairjlk: we should be able to drop that16:17
SpamapSjeblair: so you're thinking that with the merger we might have them just out there fetching trees and looking for config updates, communicating them to the scheduler?16:17
jeblairjlk: correct, a merger in v3 can be entirely on the internal network.16:17
jeblairSpamapS: exactly16:17
SpamapSI do like that, especially until we get further down the road and have scale-out schedulers16:18
jeblairSpamapS: and since we've realized we still need to do the speculative merge before sending things to the executor, that's work that mergers can do while executors do other things16:18
*** rcarrillocruz has joined #zuul16:18
SpamapStristanC: Oh cool! I didn't know you were working on a dashboard. Is there one up somewhere that I could poke at?16:18
jlkjeblair: cool. I'll toss up a review to get rid of the update functionality.16:19
*** isaacb has joined #zuul16:20
jlkjeblair: I tracked down my variants issue to a really small logic bug though, so there's that :)16:20
jeblairjlk: re nodepool/noop -- while there is special-casing of noop around the executor (so nothing is actually run), i don't think we special cased it in the nodepool interface.  actually, what should be special cased there is not noop per-se, but rather, a job with an empty nodeset.16:20
jeblairjlk: cool, that was my next question -- the list/str thing was the only variants problem?16:21
jlkwell, it was the only thing causing a traceback16:21
jeblairjlk: therefore it must be the only error, right?  :)16:22
jlkof course!  Tests passed!16:22
SpamapS"the test suite passed" is the new "it compiles"16:22
SpamapSship it!16:22
jlkI probably should have added some sort of test that caused the traceback, but... I didn't.16:23
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: WIP: add configuration documentation  https://review.openstack.org/46332816:23
jeblairmore docs from 36,000ft ^16:24
SpamapSugh. this ssh agent stuff is proving more complex than I had expected.. seems I've created some kind of race and it's manifesting as locked up test suite16:27
jeblairi'm declaring a timeout on simple changes with +2 from before summit and single-core approving them16:29
jeblair(my goal this week is to get my zuul gertty dashboard back to a managable size)16:30
jlk+116:32
*** harlowja has joined #zuul16:33
jeblairpabelanger: i'm +3ing https://review.openstack.org/451470 with a comment16:33
jlkjeblair: so I don't know how the test suite gets things to work without a nodepool. Is it not possible at this point outside of the unit test engine to convince zuul to execute a job and consider it successful? For the sake of live testing zuul driver interface code without bothering to spin up a whole functional nodepool.16:33
jeblairpabelanger: however, it looks like 451470 is based on an abandoned patch?  you want to rebase that?16:34
jeblairjlk: the test suite has a fake nodepool which satisfies those actual requests for zero-node nodesets16:34
jeblairjlk: so yeah, we need the short-circuit node request logic added to do what you want16:34
jlkahhh16:34
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Move test_test_config to a cmd-focused test suite  https://review.openstack.org/46149316:35
SpamapSjeblair: does that include gear changes? ;-)16:35
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Re-enable test_live_reconfiguration_merge_conflict  https://review.openstack.org/46150216:36
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Log return code on failed dib build  https://review.openstack.org/45078216:36
jeblairSpamapS: i wouldn't consider those trivial... i'd like mordred or clarkb to take a look, though if they decline, i'm okay with you and i being happy with them.  :)16:37
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Re-enable test_live_reconfiguration_failed_root  https://review.openstack.org/46150816:37
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Re-enable test_live_reconfiguration_failed_job  https://review.openstack.org/46151216:37
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Re-enable test_live_reconfiguration_shared_queue  https://review.openstack.org/46152216:37
SpamapSjeblair: have we ever identified any other significant users of gear?16:41
jeblairSpamapS: not that i'm aware of (which isn't to say they don't exist, they may just be quiet)... clarkb, fungi: ^?16:41
clarkbI know HPE was looking at using it for some cloud things back when they clouded things16:42
jlkI seem to recall it being a thing that Datadog can interact with, so apparently there are SOME users out there16:42
SpamapSjeblair: I was just hoping we might have somebody out there who has used gear that isn't us, and would like to try porting to the new API. I did use it for gearstore/gearhorn, which were experiments in making oslo.messaging gear drivers.. but that's still me, using my API change. ;-)16:43
jlkhttp://docs.datadoghq.com/integrations/gearman/16:43
jeblairShrews: this wants a once-over from you: https://review.openstack.org/45807316:43
fungii'm not at all aware of other consumers, but it comes as no great surprise to me if there are any16:43
jlkI'm assuming here that "gear" == "gearman" but I could be very wrong16:43
SpamapSAlso there's a group that wrote yet another gearmand port, in go, that wants to look at translating the gearman protocol into gRPC16:43
SpamapSI _really_ like that idea. :)16:44
jeblairjlk: i think SpamapS was specifically focused on the 'gear' library and the slight api modifications we are considering16:44
SpamapS(because we'd finally get usable auth for free)16:44
SpamapSjlk: yeah, gearman itself is actually all over the place, quietly, but the python gear library .. we don't know if people depend on it.16:44
SpamapSWe should assume they might16:44
SpamapSthough it is 0.x¸ so we only need to be cordial, not fanatic, about breaking things too badly.16:45
jlkoops, sorry16:45
SpamapSI believe if we had resurrected gearman earlier, it might be in use more.. but unfortunately, it fell victim to a few life challenges in its maintainer(krow)'s life for a few years.16:46
jeblairi'm still pretty comfortable with "the py2 api isn't substantially changing, you only notice with py3, and py3 was so bad earlier i kind of hope no one was using it".  but i agree, that's an entirely hypothetical construct it would be nice to realize or falsify.  :)16:46
SpamapSjeblair: I would suggest that we make the change to .name (which is a little tiny bit 2.x intrusive, for like, users of non-utf8 queue names...) release as 0.816:47
clarkbI haven't had time to look at the changes, but we aren't adding utf8 support in a set of new classes that would be backward compat?16:47
clarkb(I thought that was the plan but may have misremembered)16:47
SpamapSclarkb: that's exactly what we did.16:47
clarkboh then nothing should change for existing users right? (excluding unexpected bugs)16:47
SpamapSclarkb: but we also just made .name utf8 always, and added a binary class for those unfortunate enough to have done that evil thing.16:47
SpamapSclarkb: now that you have it top of mind....16:48
clarkbgotcha so .name is the big change16:48
jeblairright, so it's technically an api break for the one person who registered utf8 pile-of-poo as a function name16:48
SpamapShttps://review.openstack.org/46117216:48
SpamapSjeblair: actually I think it won't break that person in py216:49
jeblairSpamapS: even better :)16:49
SpamapSit would break the chinese user who used GB231216:49
SpamapSwhich would also break the python interpreter in literals...16:50
SpamapSso they'd have to have _REALLY_ tried hard to make this easy for us to break.16:50
* SpamapS may also be paying way too much attention to the corner cases here ;)16:50
SpamapSactually GB2312 is a bad example... since it is a set of code points like unicode.. and both well known encodings are ascii compatible (EUC-CN and HZ)16:51
SpamapSso yeah, corner sufficiently shrunk :)16:52
jeblairShrews: https://review.openstack.org/46333816:54
mordredyah - I just +A'd the first patch ... it seems the only people who would be broken would be py3 users. py3 users are so unlikely that I'm comfortable with the corner cases16:54
mordredjeblair: you've +2'd https://review.openstack.org/#/c/461172 before but SpamapS revised it16:54
jeblairmordred: thx, diffing16:55
jeblair+316:55
mordredjeblair: while you're at it - https://review.openstack.org/#/c/400472 too - since we're adding py3 support and those calls raise a warning in py3 - seems like it'll be annoying if we don't merge that16:56
jeblairdone16:57
mordredwow. that's everything that's not SpamapS thundering-herd patches16:57
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Python 3.x incompatible use of print operator  https://review.openstack.org/46358616:58
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove FakeFile from fakeprovider.py  https://review.openstack.org/46358716:58
SpamapSthe thundering-herd patches can definitely wait17:00
*** Cibo_ has joined #zuul17:00
SpamapSin fact I think since writing them I discovered that libgearman failed to implement the client server selection hash algorithm correctly too17:00
SpamapSfunny thing about gearman... I am pretty sure if they hadn't written a PECL PHP extension for libgearman and gotten it included early on in php's docs, it would have died a long, long time ago. PHP users keep showing up with insane gearman uses that would be entirely fine done as MySQL queries. :-P17:01
jeblairjamielennox: can you refresh https://review.openstack.org/446308 and https://review.openstack.org/447734 when you have a chance?17:10
*** isaacb has quit IRC17:12
clarkbSpamapS: ok got through https://review.openstack.org/#/c/461172/10 general shape of it seems fine. But some small belts and suspenders things noted inline17:14
jeblairpabelanger: https://review.openstack.org/452991 is out of date now i think?17:21
jeblairpabelanger: and https://review.openstack.org/45424817:21
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add some lookup plugin tests  https://review.openstack.org/45439617:23
jeblairi just dropped the WIP commit message from that.  hopefully we'll find time to add more of those tests in the future, but for now, let's just land that ^17:23
jeblairjamielennox: can you take a look at https://review.openstack.org/455508 ?17:24
*** harlowja has quit IRC17:26
jlkjeblair: oops, I reviewed your docs before you pushed patch set 2. Reviewing the new bits, but looks like my comments on version 1 stand.17:26
jeblairjlk: yes, airplanes.  ps2 is almost entirely appending new text.  i will certainly check both before doing a real revision.17:31
jlkso. much. text.17:38
*** Cibo_ has quit IRC17:45
jlkoh haha. So, looking at the merger:update function, looksl ike that gets called by the cat function, to ensure the repo is updated.17:55
jlkor, not exactly17:56
*** jamielennox is now known as jamielennox|away17:59
jlkSurprise benefit of docker-compose, once you've done an up, you can modify the container, docker-compose stop, docker-compose start and it'll run that modified container. You can modify zuul code within, restart the things and test changes!18:02
jlkdon't have to figure out how to re-build the image with the altered zuul code fetched from some staging place18:02
SpamapSclarkb: thanks!18:03
mordredjlk: I was looking atyour code file and thinking it was surprisingly well-suited for being driven by a zuul as well18:04
jlkdriven by a zuul?18:04
jlkas in the post-commit deploy stuff?18:04
mordredno - for testing ... on esec18:04
jlkoh, right. Spin up a set of containers, shove an event set through, check the results.18:05
mordredpart of the big challenge in thinking about k8s workloads is "how do you get from the source repos that zuul has prepared to those running as images in containers"18:05
*** jamielennox|away is now known as jamielennox18:05
mordredthe compose file seems to understand that sometimes you might want to work from some source repos and produce containers from those18:05
mordredso it won't actually solve the whole thing for us - but it might be a nice starting point from which to think18:06
mordredjlk: the most vexing part as I think forward - but that I'm not worrying about TOO much because we havne't actually dug in - is that k8s manifests and helm charts tend to be expressed in terms of container names. but a source repo that builds containers doesn't tend to express the name of the container it's going to build - so given a chart that needs 10 images and 2 source code repos that would provide the18:09
mordredcontainers for 2 of those - there's no real good 'automatic' way to infer the right thing to do to test the set of changes you have ...18:09
mordredjlk: now - it's VERY possible I'm _way_ overthinking this and that the answer is"the job is just going to have to have a thing that deals with conatiner builds as step one"18:09
*** dkranz_ has quit IRC18:10
*** dkranz has joined #zuul18:12
jlkyeah, I think you're a few turns farther down the road than I am at this point18:22
SpamapSI personally like the idea of build as step 118:24
SpamapS5+ years of "test the bits that you run in production" are embedded deep in my consciousness.18:25
SpamapSso if I can get from build -> [matrix of tests with same built containers ] -> publish said containers18:25
SpamapSI'd be happy as a clam18:25
jlkright18:26
jlkparticularly if it's done as gate, where zuul is testing the merge AS IT WILL HAPPEN18:26
jlkso you're essentially building containers of merged code, even if it hasn't yet "merged" in the canonical repo.18:26
jlkthe hashes won't change, in theory18:26
clarkbthey will because of timestamps unless we get to having zuul push to gerrit and only doing a single merge for all jobs for a gated change18:27
jlktimestamp causes the merge hash to change?18:28
clarkbyes18:28
jlkTIL....18:28
clarkbthis is why I dislike the cherrypick feature in git review18:28
clarkbleads to much confusion18:29
jlkSo I can't cryptographically validate that the merge of code Zuul did to perform a test is the exact same as the merge of code that zuul caused to have happen when the tests completed?18:29
mordrednope. although having zuul push the merge rather than click the merge button is a thing we've talked about many times and would allow that18:30
jeblairnot unless zuul pushes the work that it did upstream (which is a fairly easy enhancement to make and we have favorably considered doing it).18:30
mordredwhat jeblair said18:30
jeblairand mordred18:30
mordredI think at the VERY least zuul should grow that option18:30
jlkyeah that would make a lot of folks more comfortable maybe?18:31
jlkdunno18:31
mordredwhether or not openstack decides to enable it or continue to have zuul click the button in gerrit is a different question I think18:31
clarkbthere are other ways of verifying too fwiw18:31
clarkbhashes of patch diffs for example18:31
clarkb(did someone say darcs)18:31
jeblairjlk, SpamapS: we tested this with gerrit, btw -- if zuul pushes a change to a branch, gerrit will automatically close the change... it would be interesting to know if github would auto-close a PR if someone pushed the commits in that pr to the branch it was targeting.18:31
mordredI believe it does, yes18:31
jlkIt is supposed to yes18:32
jeblaircool18:32
jlkhowever...18:32
jlkI don't think the github integration API allows us to push changes.18:32
jeblairjlk: that's okay, it's just a git op18:32
jlksince it's a bot instead of ostensibly a human.18:32
jlkit's a git op, but it's more of a credentials problem on the other side18:32
jeblairjlk: oh, you're saying projects would have to allow zuul as a team member or something18:32
mordredjeblair: so - an "integratoin" doesn't have a github user account associated with it18:32
jlkthe repo owner on github would have to grant zuul the rights to push18:33
jeblairfun problem18:33
jeblair(incidentally, this is useful on its own, but is also essentially a pre-req for bidirectional cross-repo-dependencies (which are a two-phase commit problem))18:33
mordredyah. althugh the other bit is the "publish the containers I built from the commit in gate - don't re-build them in post to publish them"18:34
mordredso there are a couple of places for fun mind thinking here18:34
jeblairmordred: yeah, another thing which is easier with stable shas, but likely possible to work around18:34
jeblairi need to go get a fried chicken sandwhich before all the hipsters show up18:35
mordredjeblair: you can never beat the hipsters18:35
jlknot with that attitude you won't.18:37
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Remove unused merger:update task  https://review.openstack.org/46570118:38
jlkre earlier convo ^^18:38
jlkis there a gate_recheck in our gerrit/zuul?18:45
*** jkilpatr has quit IRC18:50
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add cachecontrol to requests to github  https://review.openstack.org/46158718:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add support for requiring github pr head status  https://review.openstack.org/44939018:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Adds github triggering from status updates  https://review.openstack.org/45384418:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement trigger require/reject-approvals  https://review.openstack.org/46338718:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement pipeline requirement on github reviews  https://review.openstack.org/45384518:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement github trigger requirement status  https://review.openstack.org/46338618:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Actually filter status triggers  https://review.openstack.org/46338518:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Create github client each time it's called.  https://review.openstack.org/46342118:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Use integration_id with github  https://review.openstack.org/46342018:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Refactor integration key loading to always load  https://review.openstack.org/46342318:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Represent github change ID in status page by PR number  https://review.openstack.org/46071618:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Decode JSON body once for requests  https://review.openstack.org/46342218:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Include tenant name in github context  https://review.openstack.org/46387118:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Save installation ids to a cache and fetch them per project  https://review.openstack.org/46342418:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Catch integration key file not found in zuul  https://review.openstack.org/46342518:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Include exc_info in reporter failure  https://review.openstack.org/46076518:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add trigger capability on github pr review  https://review.openstack.org/44936518:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Ensure PRs arent rejected for stale negative reviews  https://review.openstack.org/46070018:51
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Comment on PRs if a remote call to merge a change failed  https://review.openstack.org/46076218:51
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Extract ansible library file copying to a function  https://review.openstack.org/46570518:53
mordredSpamapS: ^^ noticed that while reviewing the first patch in your py3k stack18:54
mordredjlk, jeblair: re: recheck - it struck me yesterday (I needed to recheck a stack of changes that had all failed because of the sphinx issue)18:54
*** jkilpatr has joined #zuul18:54
mordredthat a "recheck stack" would be nice - basically if you left it on the latest change of a stack it would recheck that change and all it depended on18:55
jlkwe've got "recheck" which should cause a new +1 vote to come in, right? which would then potentially trigger gate, if other things are in place18:55
mordredit could also be a super easy DDOS - so may be a terrible idea18:55
mordredjlk: yes18:55
jlkin Bonny, we did a gate_recheck so that you could skip the check pipline18:56
clarkbbut only if you dont already have a +1 or your gerrit is newer than ours18:56
jlkoh :(18:56
clarkbbecause gerrit wont emit the +1 if its already there on pur version18:56
jlkyeah I think github is the same18:56
jlkalthough I'd have to verify that18:56
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Copy dirs to handle __pycache__ in py3  https://review.openstack.org/46389019:00
*** mordred has quit IRC19:05
*** mordred has joined #zuul19:06
pabelangerjust catching up on back scroll. Internet outage for last 4 hours19:13
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Rename nodepool.py to launcher.py  https://review.openstack.org/46380719:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Ensure zookeeper_servers is a list  https://review.openstack.org/46388019:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Use six.moves.urllib for python3 compat  https://review.openstack.org/46359519:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Update exception message handling for python3  https://review.openstack.org/46403419:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Sort flavors with operator.itemgetter('ram')  https://review.openstack.org/46399819:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Replace dict.iteritems() with dict.items() for python3  https://review.openstack.org/46402619:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Switch to next(generator) for python3  https://review.openstack.org/46404019:20
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Fix imports for python3  https://review.openstack.org/46380819:20
pabelangerShrews: jeblair: okay, I have rebased without 463594 for now19:21
pabelangerso I can read up more about it19:21
SpamapSmordred: \o/ yes I kept twitching patching those bits. Thanks!19:27
* mordred is doing funny little cleanup patches today while reviewing other things19:33
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Convert some leftover changeish mentions to ref  https://review.openstack.org/46571819:33
mordredlike that19:33
mordred(noticed while reviewing one of the github stack)19:33
* clarkb is fighting the post travel plague and trying to get useful things like operating system updates and network infrastructure changes in place before needing all that hardware later in the week19:33
*** harlowja has joined #zuul19:39
*** harlowja has quit IRC19:53
jlkweeeird. Gertty isn't showing me mordred's latest change19:55
*** harlowja has joined #zuul19:57
jeblairjlk: it has the github-v3 topic, in case you're looking at a dashboard that filters those19:58
*** harlowja has quit IRC20:00
jlkI have it showing all changes in openstack-infra/zuul20:03
jlkthe most recent number it'll show me is 46570120:03
jeblairjlk: and you're subscribed to zuul?20:03
*** jkilpatr has quit IRC20:04
jlkyeah20:05
jlkI'm going to run with logging20:05
jeblairjlk: ++20:05
jlkoh now 465705 showed up20:05
jeblairmaybe it was offline, or something was stuck...20:05
jlk2017-05-17 13:07:25,747 GET: https://review.openstack.org/a/changes/?n=500&q=project:openstack-infra/zuul -age:19s20:07
jlk2017-05-17 13:07:26,206 HTTP status code: 20020:07
*** jkilpatr has joined #zuul20:08
*** dkranz has quit IRC20:09
jlk¯\_(ツ)_/¯20:09
SpamapSjlk: I find that ctrl-o is good for those situations. :)20:09
SpamapSas in, type in the number.. and gertty goes and finds it20:10
jlkoh I think there is something weird on OSX where ctrl o doesn't work right20:11
SpamapSmaybe ask siri to press ctrl-o?20:12
jeblairjlk: yeah, you may want to remap that (there's an example for exactly that command in the sample config file)20:12
jlknod that's where I remember seeing it20:13
jlkUh, is gate-zuul-python27-ubuntu-xenial being flappy? EG https://review.openstack.org/#/c/445644/ it passed the test in check at 11:54, and then failed it in gate at 12:0020:19
jeblairjlk: hrm, looks like it was still running when it hit the timeout20:21
jeblairmaybe we just need to bump it20:23
clarkbFile "tests/unit/test_github_driver.py", line 401, in test_failed_changes <- timeout waiting for zuul to settle20:23
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Better merge message for GitHub pull reqeusts  https://review.openstack.org/44564421:04
*** dougbtv_ has joined #zuul21:19
openstackgerritMerged openstack-infra/zuul feature/zuulv3: GitHub file matching support  https://review.openstack.org/44611321:19
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Log GitHub API rate limit  https://review.openstack.org/44615021:22
*** dougbtv has quit IRC21:22
*** harlowja has joined #zuul22:02
*** jkilpatr has quit IRC22:07
*** dougbtv__ has joined #zuul22:15
*** dougbtv_ has quit IRC22:17
*** dougbtv_ has joined #zuul22:18
*** harlowja has quit IRC22:18
*** dougbtv__ has quit IRC22:20
*** jkilpatr has joined #zuul22:24
*** dougbtv__ has joined #zuul22:26
*** dougbtv_ has quit IRC22:28
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Set filter according to PR/Change in URL  https://review.openstack.org/44678222:59
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Test gerrit and github drivers in same tenant  https://review.openstack.org/44825723:00
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add support for github enterprise  https://review.openstack.org/44925823:00
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add trigger capability on github pr review  https://review.openstack.org/44936523:06
*** dougbtv_ has joined #zuul23:25
tristanCSpamapS: (re dashboard) the goal is to inspect the last few post/periodic job to ease debug, the first attempt is https://review.openstack.org/#/c/464524/23:26
*** dougbtv__ has quit IRC23:27
jeblairtristanC: cool -- we probably won't land any feature additions to the zuul v2.5 launcher -- maybe we can map that into zuul v3?23:31
tristanCSpamapS: well a better one based on the sql-reporter needs to be groomed first, I'll probably go for a basic pecan server with angular client, but perhaps that can be part of the webapp23:31
tristanCjeblair: indeed hopefully this could be ported to zuul v3, but unfortunaly the plan is to migrate from jenkins to zuul-launcher first23:33
jeblairtristanC: ++ using sql reporter.  mtreinish was also looking at using the sqlreporter inside of openstack health.23:34
jeblairi don't think he's started on that23:35
tristanCjeblair: excellent, I'll get in touch. thanks!23:35

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!