Thursday, 2017-03-02

openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Allow using webapp from connections  https://review.openstack.org/43983100:00
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Support GitHub PR webhooks  https://review.openstack.org/43983400:05
jlkauggy: thanks for reminding me to link back to a storyboard story :D00:06
auggyjlk: no prob, just don't want anyone else to pick it up and cross the streams00:22
rbergeronspamaps: sorry i couldnt join, had a dentist appointment that i already cancelled once00:39
*** jamielennox is now known as jamielennox|away01:16
jeblairjlk: yes, that is our webapp tenant isolation story to date.  it's entirely possible we may want to put real access control on that in the future.  :)  however, anticpating what you're working on -- connections/drivers are just about the only things that actually span tenants.  so i would expect a github driver to have an endpoint which did not include a tenant name.  so maybe the hooks should go under "hostname/github/<connectionname>".01:23
jeblairthe use of the word 'hostname' in that is confusing.  let's just pretend i said "/github/<connectionname>".01:25
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Re-enable test_timer  https://review.openstack.org/43096804:16
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Re-enable test_timer_smtp  https://review.openstack.org/43098304:16
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Re-enable test_idle  https://review.openstack.org/43056804:16
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Re-enable test_dependent_behind_dequeue  https://review.openstack.org/43707604:16
SpamapSjeblair: ^ addressed comment on 43056804:16
*** yolanda has quit IRC05:35
*** Cibo_ has joined #zuul06:19
*** saneax-_-|AFK is now known as saneax06:26
*** saneax is now known as saneax-_-|AFK06:52
*** saneax-_-|AFK is now known as saneax07:02
*** Cibo_ has quit IRC07:20
*** isaacb has joined #zuul07:22
*** saneax is now known as saneax-_-|AFK07:24
*** Cibo_ has joined #zuul07:28
*** saneax-_-|AFK is now known as saneax07:32
*** Cibo_ has quit IRC07:34
*** isaacb has quit IRC07:56
*** isaacb has joined #zuul07:59
*** hashar has joined #zuul09:11
*** isaacb has quit IRC10:19
*** isaacb has joined #zuul11:10
*** Cibo_ has joined #zuul11:36
*** wznoinsk has quit IRC12:39
*** Shrews has quit IRC13:11
*** Shrews has joined #zuul13:15
Shrewsoh neat. we can now access zuulv3 logs  \o/13:22
*** Cibo has joined #zuul13:34
*** Cibo_ has quit IRC13:34
*** Cibo has quit IRC13:46
*** saneax is now known as saneax-_-|AFK13:58
*** isaacb has quit IRC14:58
pabelangerShrews: yar!15:05
pabelangerwouldn't mind some eyes on https://review.openstack.org/#/c/439637/ this morning, currently jobs are capped at 6min run times15:06
mordredlook, it's a Shrews !15:08
mordredShrews: while you were gone, we rewrote nodepool in haskell - hope that's ok15:09
*** Cibo has joined #zuul15:17
Shrewsmordred: totes15:26
*** isaacb has joined #zuul15:55
*** isaacb has quit IRC16:04
*** yolanda has joined #zuul16:05
*** hashar has quit IRC16:20
Shrewsjeblair: I'd like to clarify this part of your algorithm: "If request < quota and request > available nodes (due to current usage), begin satisfying the request and do not process further requests until satisfied"16:43
Shrewsjeblair: Does that mean "go ahead and exceed max_servers to satisify this one request, ignoring other requests until this one is done"?16:44
Shrewsjeblair: Or does it mean "spin on this request until the needed number of nodes appear"?16:44
Shrewsi'm guessing the 2nd, but want to verify16:45
Shrewswell, "spin + ignore others"16:48
*** Cibo has quit IRC16:48
jeblairShrews: yes, the second.16:50
Shrewsjeblair: ok. will have to come up with a clever way to flag such a situation. thanks16:51
Shrewsugh, this might actually be a bit complicated. yay for returning to work!16:57
Shrewsah, i think moving the quota and availability checks up from NodeRequestHandler to the parent ProviderWorker makes this easy17:10
pabelangerjeblair: nice email. I like the trusted-projects / untrusted-projects changes to yaml17:50
jeblairShrews: that sounds reasonable17:53
jeblairpabelanger: ah thanks.  also, folks in channel, i sent an email to openstack-infra@lists about some proposed changes to clarify confusion around having projects from multiple sources in the same pipelines and depending on each other and such.17:54
Shrewsi concur re: the trusted-projects/untrusted-projects label change18:02
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Report layout config errors for config repos  https://review.openstack.org/44076018:52
jeblairwhen we land that change and its parent, it should be safe to throw whatever garbage we want at our running zuulv3 and it will throw it right back at us!18:52
jeblair(in case it's not clear: that is a desirable thing)18:53
*** Cibo has joined #zuul18:57
pabelangercool 439637 would be nice to get too19:09
*** hashar has joined #zuul19:38
*** hashar has quit IRC19:42
*** hashar has joined #zuul19:42
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Correct the quota/availability algorithm  https://review.openstack.org/44078019:43
jlkOh boy, somehow I got tests to non-stop be executing git commands in popen, really really fast. No real errors visible. GOOD TIMES19:46
jeblairjlk: i should document my tips for running zuul tests on a tmpfs...19:48
jlkduring tox tests does zuul services log anywhere ?19:50
clarkbjlk: yes to a logging fixture which injects the logs into the subunit. On successes you won't see it, but on failures its all printed to stdout19:51
jlkI'm just seeing InterruptedError() occasionally from RPCListner19:51
clarkbjlk: to find the successes look in .testrepository/$number19:51
clarkbor commands like testr last --subunit iirc19:52
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Report layout config errors for config repos  https://review.openstack.org/44076019:57
jeblairjlk: InterruptedError is normal; we should trap it and ignore it.  it's part of the shutdown.19:59
jlkoh.19:59
jlkthen I don't know why tests are doing this.19:59
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Support GitHub PR webhooks  https://review.openstack.org/43983420:00
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Catch gear.InterruptedError  https://review.openstack.org/44078920:02
*** jamielennox|away is now known as jamielennox20:02
jeblairjlk: ^ i had developed a blindness to that.  thank you for reminding me it's annoying.  :)20:02
openstackgerritCullen Taylor proposed openstack-infra/zuul feature/zuulv3: Re-enable test_tags  https://review.openstack.org/43985820:48
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Catch gear.InterruptedError  https://review.openstack.org/44078920:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Report layout config errors for config repos  https://review.openstack.org/44076020:50
rcarrillocruzpst pst20:51
* rcarrillocruz uber excited that just saw Zuul v3 mentioned in an Ansible 2.4 roadmap20:51
pabelangerrcarrillocruz: woah, URL?20:53
rcarrillocruznot public :P20:54
rcarrillocruzit appears is been pushed for 3rd party CI on vendor modules20:54
rcarrillocruzmordred, Shrews ^20:54
rcarrillocruzi'm told you're pushing for it20:54
rcarrillocruzand just volunteered to get stuff assigned20:55
rcarrillocruzi mean, I volunteers20:56
rcarrillocruzd20:56
rcarrillocruzi can't even type20:56
Shrewsi'm not aware of timelines around that. it may be speculation21:00
clarkbwhen is 2.3 happening so wr can have sync retries that work?21:01
* clarkb is only slightly impatient :)21:01
rcarrillocruzhah21:04
pabelangerclarkb: Shrews: mind a review on 43963721:18
clarkbpabelanger: is that just pulled over from v2.521:28
clarkb?21:28
pabelangerclarkb: ya, built on from v2.5, but some changes21:29
pabelangerto watchdog21:29
pabelangerbasically, we support jobs that run forever now21:29
pabelangerand remove 5m buffer to abort jobs21:30
clarkbbecause ansible is responsible for running job and copying logs ya?21:31
pabelangerright, we better control that in post-run21:33
clarkbpabelanger: I approved but also left the tiniest of nitpicks for possible followup21:39
pabelangerclarkb: ack21:40
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add timeout variable to jobs  https://review.openstack.org/43963721:47
pabelangerjeblair: Shrews: clarkb: objections to restarting zuulv3-dev to pick up^?21:49
clarkbnone from me21:49
ShrewsNope21:49
pabelangerdanke21:51
jeblairpabelanger, clarkb, mordred: can you review 439887 and 440760 so we can have config error reports? :)21:52
rbergeronthere are no errors! everythign is perfect21:53
*** anteaya has quit IRC21:54
pabelangerjeblair: I can shortly21:55
*** bstinson has quit IRC21:55
jeblairrbergeron: zuul will go into an infinite loop telling itself that right now :)21:57
*** bstinson has joined #zuul21:59
clarkbjeblair: maybe I don't have enough sugar today but where is the error in the yaml at https://review.openstack.org/#/c/439887/3/tests/unit/test_v3.py ?22:07
*** anteaya has joined #zuul22:07
jeblairclarkb: it's where it says "foo: error"22:08
* jeblair hands clarkb a chocolate bar22:08
clarkbbecause foo isn't a valid key?22:08
jeblairya22:09
jeblairmaybe i should have said "error: foo"22:09
jeblairclarkb: i copied the full error report into the gerrit comments, so you can see what it look like22:09
*** hashar has quit IRC22:12
clarkbjeblair: thanks. Also is it worth having a test where the yaml itself is invalid?22:13
jeblairclarkb: probably so, i'll add one in a followup22:13
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add generic tox job  https://review.openstack.org/43828122:21
pabelangerjeblair: I think I'm ready to report a feature request! With^ we now have duplicate playbooks, because job names have to point to a playbook. Maybe we can also add a job.playbook key to be used, if defined, otherwise fall back to job.name for the playbook?22:24
jeblairpabelanger: it's called 'job.run'22:29
pabelangerYay!22:29
jeblairpabelanger: but what are the duplicate playbooks?22:30
pabelangertox-cover, tox-linters, tox-py27 right now22:30
pabelangerbecause of the way they are setup22:30
pabelangerhowever, moving forward they might grow specific actions22:31
jeblairpabelanger: why not 3 playbooks and put the argument to the tox role in the playbook rather than the job?22:32
pabelangerjeblair: so, that is how I initially did it. But, now that we have job.vars, I could abstract that out more to a single playbook22:33
pabelangerjeblair: PS9 did that22:33
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add generic tox job  https://review.openstack.org/43828122:34
pabelanger^would be another way.22:34
pabelangerdon't have a preference at this point22:35
pabelangeraside from flexing parts of zuulv322:35
mordredyah - seems like playing with both approaches to learn which thing 'feels' better is worthwhile at this point22:37
pabelangerthe upside I think for 3 playbooks, with vars included, makes it easier for other zuulv3 to consume. Which, is something we want22:39
jeblairtrue.  i think when it comes down to it, i'm going to have a preference that our fundamental jobs be really clear and easy to understand without too much ansible magic.  i'd like us to have something to point to where a simple job is as easy to understand as jjb.22:39
jeblairit's the complicated jobs (ilke devstack) where the extra magic makes it *easier* to understand than jjb :)22:39
pabelanger++22:39
mordredyah22:39
pabelangerlet me revert to PS922:40
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add generic tox job  https://review.openstack.org/43828122:41
pabelangerokay, have to run errands with family. Plan to do some more hacking this evening22:42
jeblairpabelanger, mordred: i think it might be nice to have one or more competing changes for how to set up those tox jobs, and to try to get each approach looking the best.  i think that might be the best way to do what mordred describes and achieve our goal.22:58
jeblairpabelanger: so start with a change for the PS9 approach, and another for PS10, and iterate on both of them for a bit22:58
jeblairpabelanger: okay, i left a bunch of comments on that change with things that may apply to either of those approaches.  i think if you can incorporate those and make 2 new changes, we'll be off to the races.23:03
*** saneax-_-|AFK is now known as saneax23:20
jlkwooo, SO MANY LINES. This log has too many lines to open it in the browswer.23:32
jlkis there a easy RTFM for running a subset of tests with tox?23:33
*** jamielennox is now known as jamielennox|away23:37
jeblairjlk:  the TESTING file has suggestions on how to run one test in the foreground.  i think you can give a pattern match to testr to run a set.23:38
jlkoh hey look at that, I didn't read far enough. Derp.23:39
pabelangerjeblair: agree, I'll iterate on the comments23:44

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