Thursday, 2016-12-15

openstackgerritMerged openstack-infra/nodepool: Add missing pause fields to config-validate  https://review.openstack.org/41099200:34
openstackgerritMerged openstack-infra/nodepool: Add missing pause fields to config-validate  https://review.openstack.org/41100400:52
openstackgerritMerged openstack-infra/nodepool: Validate configs when used by tests  https://review.openstack.org/41099500:52
*** jamielennox is now known as jamielennox|away00:58
*** jamielennox|away is now known as jamielennox01:00
*** jamielennox is now known as jamielennox|away02:36
*** jamielennox|away is now known as jamielennox02:51
*** harlowja has quit IRC03:03
*** saneax-_-|AFK is now known as saneax04:46
*** saneax is now known as saneax-_-|AFK05:12
*** saneax-_-|AFK is now known as saneax05:17
*** abregman has joined #zuul06:10
*** hashar has joined #zuul07:40
*** hashar has quit IRC08:04
*** hashar has joined #zuul09:35
*** openstackgerrit has quit IRC10:18
*** abregman is now known as abregman|afk12:37
*** openstackgerrit has joined #zuul12:49
openstackgerritMerged openstack-infra/zuul: Fix retry accounting off-by-one bug  https://review.openstack.org/40881412:49
openstackgerritMerged openstack-infra/zuul: Re-enable test_nonvoting_job  https://review.openstack.org/41037613:01
openstackgerritMerged openstack-infra/zuul: Re-enable test_no_job_project  https://review.openstack.org/41037813:03
*** abregman|afk is now known as abregman13:16
*** saneax is now known as saneax-_-|AFK13:23
rcarrillocruzafk for a while, picking my son14:37
rcarrillocruzlaterz14:37
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Remove ZK lock variables  https://review.openstack.org/41085314:56
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Share single ZooKeeper object among workers  https://review.openstack.org/41136014:56
Shrewslet's see what ^^^ breaks14:57
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Share single ZooKeeper object among workers  https://review.openstack.org/41136015:40
mordredShrews: woot!15:46
*** abregman has quit IRC16:01
Shrewswell that change is failing spectacularly16:12
*** Cibo_ has quit IRC16:18
*** Cibo_ has joined #zuul16:23
mordredShrews: that means you did something right16:34
*** hashar has quit IRC16:35
Shrewsthey pass individually on my local machine, so... weird16:43
clarkbresource contention between parallel tests?16:44
Shrewsgotta be something with the test setup that i missed. all of the test_builder tests passed, but test_commands.py and test_nodepool.py (both needing ZK connections, too) failed.16:49
Shrewsoh, i think i see it16:57
*** ajafo has quit IRC17:09
*** ajafo has joined #zuul17:10
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Share single ZooKeeper object among workers  https://review.openstack.org/41136017:10
openstackgerritJames E. Blair proposed openstack-infra/zuul: Fix test_rerun_on_abort  https://review.openstack.org/41142617:25
jeblairSpamapS, jhesketh, mordred: would you please all review 411426?  and in the future, please assume that the tests are correct and carefully evaluate behavior to the contrary.17:27
Shrewspabelanger: jeblair: Can you guys think of a way we could test 411360 w/o disrupting production?17:49
clarkbShrews: maybe apply it to one of the two builders17:51
clarkbat least that way if it breaks we just turn that one off for a bit17:51
Shrewsclarkb: oh, that's a good idea17:52
pabelangerYa, we could do that17:52
clarkbbut also, lean on the integration test. Its pretty good at catching the high level things17:52
clarkbupdate as necessary to exercise the important bits17:52
pabelangermaybe we should add a 2nd provider to our devstack test17:52
Shrewsi still worry about possible ZK data corruption by just upgrading one of the builders. maybe i could super stress my 12G RAM laptop by running devstack and zookeeper and a builder17:57
Shrewsugh17:57
pabelangerI could give it a go in my local env18:08
pabelangeronce I get centos-7 working again18:08
greghaynesShrews: it shouldnt be hard to write some multithreaded zk client unit tests if youre really worried. ISTM that as long as kazooclient is reentrant it shouldnt be an issue18:10
greghaynesleft a doc comment, though18:10
Shrewsgreghaynes: oh, good eye18:11
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Share single ZooKeeper object among workers  https://review.openstack.org/41136018:12
jeblairShrews: it looks like kazoo set_hosts updates the host list but does not change the connection status.  it has 'undefined' behavior if you set it to a completely disparate zk cluster.  i think that's all fine, as it should let an operator gracefully (or as gracefully as possible) rotate a zk configuration (eg, add or drop a server).  and we can just note in the docs that if you want to do something different, like switch to a new cluster, you ...18:25
jeblair... should restart nodepool.18:25
jeblairShrews: does that sound right to you?18:26
*** harlowja has joined #zuul18:31
jeblairShrews: minor point in 411360 -- why create the zk for the builder in the test?  why not just let the builder create its own client, and have the tests use their own client?  that would let us automatically exercise the client creation code in the tests; and i'm not really worried about the tests having an extra connection open.18:33
Shrewsjeblair: i *think* what the client will do with a totally *new* set of hosts is remain connected to the old cluster, unless the old cluster goes away, in which case it should automatically use the new cluster18:44
Shrewsjeblair: so, if indeed you do switch hosts, and the old cluster remains active, then yes, a restart will be needed18:44
jeblairShrews: that makes sense.  caveat operator.  :)18:44
Shrewsjeblair: as for your minor point, it seemed like keeping all of the kazoo specifics contained to the ZooKeeper class made most sense to me (builder doesn't need to know how to create a kazoo client, and the fact that it is kazoo should remain hidden as best as possible IMO)18:46
Shrewsplus, this seemed like shortest-path-to-success18:47
Shrews:)18:47
jeblairShrews: er, i may have not communicated that well -- see my note on the change where i think i phrased it slightly differently18:49
jeblairShrews: it's more about not special-casing the test path18:49
Shrewsjeblair: oh! (words words)18:49
Shrewsjeblair: so, the builder's zk is based on the config values only. we need the per-test chroot for the tests18:50
Shrewsthat's why the tests pass a zk object in18:50
jeblairShrews: don't we interpolate the chroot into the config in the tests?18:50
Shrewsjeblair: the chroot is randomized for each test18:50
jeblair(i think that's how the workers got their zk client before, iirc)18:50
ShrewsChrootedZKFixture or something18:51
jeblairShrews: yeah, but we splat the chroot into the text fixture config before using it18:51
Shrewsdo we?18:51
Shrewsi don't see that18:52
jeblairShrews: http://git.openstack.org/cgit/openstack-infra/nodepool/tree/nodepool/tests/__init__.py#n41518:52
jeblairso anything with setup_config will do that18:52
*** harlowja has quit IRC18:52
Shrewsjeblair: oh, well that changes e'erthang18:53
pabelangerso, alien-image-list is broken18:58
pabelangerwe're not properly resolving our diskimage names18:58
jeblairwhoopsie18:58
pabelangerwere also duplicating data too18:58
pabelangerhttp://paste.openstack.org/raw/592533/18:58
clarkbpabelanger: what do you mean by resolving names?18:58
pabelangerclarkb: were trying to use template-ubuntu-xenial-1481225253 for example to search data in zookeeper18:59
pabelangerwhen it should be just ubuntu-xenial18:59
clarkb(also keep in mind that osic is a single cloud with 3 providers in nodepool so that particular one will be funny)18:59
jeblairpabelanger: remember that we actually should have alien images atm since we haven't (iirc) deleted the mysql builder images19:00
jeblair(alien images that *look like* nodepool images, even)19:00
pabelangerjeblair: I think http://git.openstack.org/cgit/openstack-infra/nodepool/tree/nodepool/cmd/nodepoolcmd.py#n227 is the reason we don't actually see the old iamges right now19:01
pabelangerif you use alien-image-list on nodepool.o.o, you just see the current images we have uploaded with nb01 and nb0219:02
clarkbah yes we needed a way to filter out the cloud images and we did ^19:02
clarkbbut if old code didn't do that then ya19:02
pabelangeryup19:03
* clarkb adds better distinction between cloud images and user images in the cloud grumps etherpad19:03
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Share single ZooKeeper object among workers  https://review.openstack.org/41136019:04
pabelangerwe might need to also upload the diskimage name into meta data too19:04
openstackgerritMerged openstack-infra/zuul: Add update storyboard script  https://review.openstack.org/40722919:08
pabelangeryup test_alien_image_list_empty is failing, but passing19:17
openstackgerritAdam Gandelman proposed openstack-infra/zuul: Add new v3 test_dyanmic_config_conflict (WIP)  https://review.openstack.org/41146719:19
openstackgerritAdam Gandelman proposed openstack-infra/zuul: Add new v3 test_dyanmic_config_conflict (WIP)  https://review.openstack.org/41146719:24
openstackgerritPaul Belanger proposed openstack-infra/nodepool: Clean up alien-(image-)list tests  https://review.openstack.org/41147019:28
pabelangerclarkb: ^ okay, fixes our tests but doesn't fix alien-image-list yet19:29
mordredclarkb: to be fair - there IS a distinction between images uploaded by the cloud and images uploaded by us - visibility=Public | is_public=True will only be set for provider provided images, and is_public=False|visiblity=Private will be for ours19:41
clarkboh then maybe we should filter on that?19:42
mordredpabelanger, clarkb: it's possible we should combine an amount of filtering on those attributes with what we're doing now19:42
mordredyah19:42
clarkbI don't know that we want to combine thenm19:42
* mordred goes to make patch19:42
clarkbwhat we want is the list of all images that were not uploaded by the cloud provider19:42
mordredyah19:42
clarkbthen remove what nodepool is using from that list and the rsult is the aliens19:42
openstackgerritMonty Taylor proposed openstack-infra/nodepool: Use is_public to determine vendor images  https://review.openstack.org/41147319:46
mordredclarkb: something like that ^^19:46
pabelangerOh, haha. I see another issue19:49
ShrewsSo, according to testr FAQ (https://wiki.openstack.org/wiki/Testr#How_can_I_run_just_one_test.3F_Just_some_tests.3F), I should be able to run multiple tests through tox like so: tox -epy27 -- '(TestNodepoolCMD|TestZooKeeper)'19:49
clarkbmordred: yup19:49
mordredpabelanger: fwiw, properties and metadata are the same, but metadata is a backwards compat field and properties is in the data model contract19:49
clarkbShrews: yes19:49
Shrewsbut that only runs the first matching tests (TestZooKeeper class tests are not run)19:49
mordredpabelanger: did you hit something not being able to find image['properties'] ?19:50
* clarkb attempts to run tests via regex locally19:51
Shrewswhere's robert collins when you need him...19:52
clarkbShrews: it ran both for me...19:52
clarkbShrews: http://paste.openstack.org/show/592538/19:53
pabelangermordred: yes, our fakes: https://review.openstack.org/#/c/411470/19:53
Shrewsclarkb: oh, nm. i am teh dumb19:53
clarkbtox -e py27 -- '(TestNodepoolCMD|TestZooKeeper)'19:53
clarkbis what I ran19:53
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Share single ZooKeeper object among workers  https://review.openstack.org/41136019:53
mordredpabelanger: yah - we should fix the fakes :)19:53
Shrewsclarkb: all the slowest tests reported were from one class. silly me didn't check logs19:54
pabelangermy, haha, was a mistake. Thought I see an issue someplace else19:55
mordredoh - well -19:55
mordredI see an issue we should fix19:55
mordredlet me send up a quick patch - we're still returning objects from our fakes in our fake provider19:55
pabelangerya, was just going to ask if shade had something we could use19:56
mordrednot anything marked as public - but maybe it's time to do that next19:56
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Share single ZooKeeper object among workers  https://review.openstack.org/41136019:56
openstackgerritPaul Belanger proposed openstack-infra/nodepool: Use provider images from yaml for alien_image_list  https://review.openstack.org/41148720:28
pabelangerjeblair: clarkb: mordred: Shrews: ^ I think is part of our fix for alien-image-list20:28
pabelangertested it, and we did leak an image in infracloud-vanilla for xenial20:30
jeblairPSA i just changed 410853 411360 411470 411473 411487 to topic:zuulv320:34
pabelangersorry about that20:36
clarkbpabelanger: do you not need to pass provider.images[name] or .name in the build lookup?20:36
* clarkb digs into zk.py20:37
mordredok. nothing is set up in the tests to provide the ability for alien_image_list to throw a failure20:37
clarkbpabelanger: ya getBuildNumbers takes a string of the image name20:37
mordredthe monkeypath in that test isn't going to work becau ethe FakeOpenStackCloud is already instantiated in setupFakes20:37
mordredwe need to be able to pass in a should-fail attribute somewhere20:38
mordredbut since it's alien-image-list, there isn't a great place from which to do that20:38
clarkbmordred: why would alien_image_list throw a failure?20:39
mordredclarkb: no idea20:39
mordredbut there is a test: test_alien_image_list_fail20:39
mordredwhich pabelanger has a patch up to try to fix - since it just always passes20:39
clarkbhuh20:39
mordredI think we could make it fail20:40
clarkbI mean it either lists images or it doesn't20:40
mordredbut I'm not sure what that'll get us20:40
clarkbmordred: right20:40
mordredother than testing the test suite20:40
openstackgerritMonty Taylor proposed openstack-infra/nodepool: Use is_public to determine vendor images  https://review.openstack.org/41147320:41
clarkbmordred: I think the tests we want are no aliens and some aliens20:41
clarkbdouble points if you can set them up to come from mars20:41
mordredhahahah20:42
pabelangerjust tested is_public, that worked as expected20:42
mordredpabelanger: yay!20:42
mordredclarkb: any thoughts on how to get an alien image into the FakeOpenStackCloud?20:47
pabelangerjeblair: clarkb: left a comment on 411487, can you advise20:47
clarkbmordred: I think you just edit the images list directly in the test20:47
mordredclarkb: how? there's not a handle to the cloud object ...20:48
clarkbmordred: fakecloud.images.add(whateveralienlookslike)20:48
mordredoh - wait - I've got an idea20:48
jeblairmordred, clarkb, pabelanger: i believe that test was originally testing that it *did not* raise an exception on failure.  of course, changes to the fake cloud stuff probably caused that to silently stop working, so a fix should probably make sure it actually runs :)20:48
jeblairpabelanger: oh, derp.  i neglected to realize you were iterating over a dict, so you *are* getting name strings there.  cc clarkb20:49
clarkbpabelanger: I think using image.name is more explicit than side effecting .values20:49
clarkboh now I grok20:49
clarkbp.images[i.name] = i is why it works ok20:50
* clarkb updates vote20:50
jeblairyeah, so 3 choices: a) as-is, b) .keys() with 'image' to be more specific, or c) .values() and 'image.name'20:50
jeblairany work for me, so +220:51
clarkbya I have approved20:51
pabelangerneat :)20:51
clarkbmordred: the fake cloud takes an images list in its constructor20:52
mordredright. but I don't operate the fake cloud20:52
clarkbmordred: if you look in test_commands there is an example of patching things to do stuff with server listing20:53
clarkbyou can also patch out the thing that returns the fake cloud in __init__.py or similar20:54
clarkbor possibly update setUpFakes to pass in an images list somehow20:54
clarkbI am not sure what the least bad choice is :)20:54
mordredthat's probably what I need to do -the setUpFakes thing20:55
mordredI do not see anywhere in test_commands where we manipulate the data returned from FakeOpenStackCloud20:55
clarkbmordred: oh its these alient list tests20:56
clarkbso maybe my version is old and yours has been updated?20:56
mordredclarkb: which test you looking at?20:56
jeblairperhaps it would be safe for a fakeopenstackcloud to always have some fake leaked images?20:56
jeblairalso some public ones20:56
mordredjeblair: I think the problem I'm running in to is that I don't know how to , in a test, get a hold of the fake cloud instance so it can be manipulated20:56
clarkbmordred: test_alien_list_fail has the patching20:57
mordredclarkb: that doesn't work20:57
clarkbmordred: ya because object is already made?20:57
mordredclarkb: ++20:57
jeblairmordred: yeah, i was saying maybe we can have it always have the images -- like it creates them in the constructor.  but i guess that really only inverts the problem (we would not be able to have a test with 0 leaked images)20:57
clarkbI think it would work if you changed it to patch the object itself20:57
mordredjeblair: so we can have it always have leaked instances, but then we can't test the negative case20:57
clarkbbut digging that out may be unfun20:57
jeblairmordred: right :)20:57
mordredexactly20:57
mordredclarkb: the object is returned from a closure20:57
mordredclarkb: so there is no handle to the object - it's not a self property anywhere :)20:58
* mordred pokes some more20:58
mordredI have a whole new very stupid idea20:58
clarkbmordred: right what you would do is replace what that closure replaces20:59
clarkbmordred: you'd repatch nodepool.provider_manager.ProviderManager._getClient with your own closure or whatever20:59
jeblairmordred: test_image_upload_fail swaps out the fakeopenstackcloud class20:59
jeblairclarkb: i *think* that may be what that test does20:59
openstackgerritMerged openstack-infra/nodepool: Use provider images from yaml for alien_image_list  https://review.openstack.org/41148721:00
mordredjeblair: it does not actually do that though21:00
mordredjeblair: I mean, it does - but it does it after the fake_client has been instantiated21:00
mordredI havea solution though - one sec21:00
jeblairmordred: gotcha21:00
clarkbmordred: that should be fine though21:00
clarkbyou have to do it bfore the useNodepool stuff21:01
jeblairmordred: yeah, you could instantiate the fake client in the get_fake_client method21:01
clarkbas that is what instantiates all the things outside the tests21:01
mordredhttp://paste.openstack.org/show/592550/21:01
mordredthat ^^21:01
mordredgives me a handle I can manipulate21:01
jeblairmordred: that's nice21:01
mordredjeblair: I'm sad it took me so long to realize I can just do that :)21:02
mordredyou should have seen the mental gymnastics I was doing21:02
jeblairi wonder if test_image_upload_fail could use that too?21:02
mordredyup21:02
Shrewsmordred: hah, you are (were?) doing the gymnastics i was doing a few weeks back when i was considering that problem21:04
Shrewsnever got around back to it, but glad you did21:05
*** Kitty- has joined #zuul21:05
clarkbboth methods are roughly equivalent, they both change the return value of get one cloud21:05
clarkbthis is definitely nicer to read though21:06
mordredHAHAHAHAHAHAHHAHAHA21:17
mordredugh21:17
mordred*HEADDESK*21:17
pabelangerclarkb: also, is there any reason not to have alien-image-delete/purge?21:19
clarkbpabelanger: yes, the osic situation21:21
pabelangerAh, ya. Keep forgetting about that21:21
clarkbits really easy to delete in bulk with the alien output as is too so not sure we want the real foot gun21:22
clarkbpabelanger: alient-image-list > file ; review file ; for image in cat file ; do openstack image delete $file ; done21:22
pabelangerya21:22
jeblairperhaps we should have it include all known images when removing images from the set, not just ones in that provider21:23
pabelangerinteresting21:24
clarkbthat is one option, though it potentially makes alien listing less accurate21:24
clarkbdepending on how you look at the output21:24
mordredclarkb, jeblair: I have things a little further, but it's eluding me21:24
mordredI'm going to push up what I've got21:24
mordredwell - two local things first21:26
pabelangerclarkb: jeblair: would it be a lot of work to update nodepool-builder now to handle the osic-cloud1 use case properly now?  EG: 1 ubuntu-xenial upload over 321:26
pabelangersomething like provider groups21:27
mordredmaybe when we rework launchers21:27
mordredwe can express "this is a cloud that should have an image uploaded to it" and "this is a profile on that cloud with different flavor/az information in it that we should launch nodes in"21:28
mordredthe same issue came up with hpcloud back in the day21:28
clarkbpabelanger: mordred ya I think its a launcher thing more so than a builder thing21:28
pabelangerk, something we should keep in mind21:30
clarkbmordred: I like the idea of profiles21:30
clarkbthe tricky bit to represent is going to be flavor to image stuff potentially21:31
clarkbwithout ending up copying image lists to represent all the things21:31
mordredyah21:31
mordredwell, we haven't ever had any specific relationship between flavors and images before have we?21:32
mordredwe've had "use these 3 different flavors" on osic and "use these three different azs" on hpcloud - both of which are just different parameters to pass to create_server21:32
clarkbmordred: we do since the image list is where you list your flavor details21:32
Shrewspabelanger: jeblair: on the single ZK connection change... I won't be around most of the day tomorrow (traveling to snowy WV) if you happen to test the change then.21:33
Shrewsbut i'm almost 10% sure it will work perfectly and without issues21:33
Shrewsmaybe 1121:33
jeblairShrews changes go to 1121:36
openstackgerritMonty Taylor proposed openstack-infra/nodepool: Use is_public to determine vendor images  https://review.openstack.org/41147321:36
openstackgerritMonty Taylor proposed openstack-infra/nodepool: Remove FakeProviderManager  https://review.openstack.org/41151221:36
mordredjeblair, clarkb: ^^ so 411473 - if you run nodepool.tests.test_commands.TestNodepoolCMD.test_alien_image_list_alien21:37
mordredin the stdout it _looks_ to my eyeballs like it's showing images in the alien list output21:37
mordredbut I also may just be silly21:37
mordredand missing something really obvious21:38
jeblairmordred: you're going to like this21:39
jeblairmordred: the fact that it looks like it's working means it's not working21:39
mordredjeblair: _excellent_21:39
mordredjeblair: how silly of me :)21:39
jeblairmordred: the assert list methods monkepatch prettytable21:39
jeblairmordred: and as part of that, it means that nothing should show up in the table21:40
mordredah21:40
jeblairmordred: (but i added a debug statement so you can see what *would* have been in the table)21:40
jeblairmordred: when i run it i see 2 table outputs21:40
jeblairmordred: http://paste.openstack.org/show/592554/21:41
mordredjeblair: yes. that is what I also see21:41
mordredjeblair: so that's good at least21:41
jeblairmordred: the second is what happens when the prettytable monkepatch thing happens, the first must not be monkepatched21:41
mordredit gives me a new place to go put a bunch fo swear words in print statements21:41
mordredwell - the _first_ thing does not show me the extra image I put in to the image list either21:42
mordredoh. duh. of course it doesn't21:42
mordredone sec - lemme see if I can at least get that to show up21:42
mordredI added a public alien image which means I did _not_ add an alien image21:42
jeblairmordred: it looks like your test is running the list command twice21:43
mordredand things approrpiately did not show the provider image21:43
jeblairmordred: assert_alien_images runs the command (with the prettytable mock)21:43
jeblairmordred: so that's the second output.  the invocation of the command in the test isn't necessary (that's the first output)21:43
mordredthe nodepoolcmd.main() ?21:44
jeblairyep21:44
jeblairand patch argv21:44
jeblairassert_alien_images does all that21:45
mordredDEBUG:tests.PrettyTableMock:['fake-provider', 'Fake Alien', 'alien-image']21:45
mordredDEBUG:tests.PrettyTableMock:['fake-provider', 'template-fake-image-1481838296', '17f62c9c281d4ae3a2f9b8300a0f6b8f']21:45
jeblairvia assert_alien_images_listed via assert_listed21:45
mordredwoot. - I mean - at least a thing I made showed p in the thing21:45
jeblair++21:45
jeblairwe can drop assert_alien_images; that seems pretty specific to a single test21:46
mordredOH! I need to pass in the id I'm looing for21:47
* adam_g emerges from from a rabbit hole21:49
openstackgerritAdam Gandelman proposed openstack-infra/zuul: Fix conflict detection and reporting for in-repo configs  https://review.openstack.org/41146721:49
openstackgerritMonty Taylor proposed openstack-infra/nodepool: Use is_public to determine vendor images  https://review.openstack.org/41147321:53
mordredjeblair: BOOM ^^21:53
mordredjeblair: thanks for the help- I'm sure I would have gotten there _eventually_ with enough curse words in print statements, but it likelu would have taken quite a while and I would have thrown something21:53
openstackgerritPaul Belanger proposed openstack-infra/nodepool: Drop 'template' from default value of template-hostname  https://review.openstack.org/41151521:59
jeblairadam_g: just finished looking over https://review.openstack.org/409376 -- one comment inline -- let me know if that makes sense  (cc mordred SpamapS)21:59
jeblairmordred: throw me a brisket?22:00
mordredjeblair: yes. I agree with your comment22:01
mordredjeblair: I don't have a brisket today - but I do have a nice looking picanha22:01
adam_gjeblair: yeah, that makes sense. i might actually rebase that on top of 41146722:01
mordredjeblair: that's this one: https://en.wikipedia.org/wiki/Picanha22:02
pabelangernow I want a picanha22:09
SpamapSjeblair: ACK22:17
*** Kitty- has quit IRC22:37
*** Kitty- has joined #zuul22:37
*** saneax-_-|AFK is now known as saneax22:40
*** saneax is now known as saneax-_-|AFK22:48
Shrewsmordred: that does not look like it would be the tastiest cut of meat, but it's still cow, so i want some22:58
jeblairadam_g: left some comments on 41146722:58
*** saneax-_-|AFK is now known as saneax23:03
SpamapSmmmmmmmmmm fatty Picanha23:05
SpamapSthey have that at the brazilian steakhouse in Tarzana.. mm23:06
mordredShrews: oh - it's actually the tastiest cut of meat23:20
*** Kitty- has left #zuul23:28
adam_gjeblair: thanks23:33
adam_gjeblair: so yeah, im definitely conflating the speculative merges with landing merges.23:38
adam_gwill need to dig in a bit further23:38
adam_gbut AFAICS the gist of 411467 is gonna be needed if the schedulers going to be catching and reporting conflicts for all changes23:39
*** jamielennox is now known as jamielennox|away23:46
*** jamielennox|away is now known as jamielennox23:50
*** harlowja has joined #zuul23:58

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