Monday, 2019-02-18

SpamapSI think we may need to use the lower level non-react-aware library to do it right.00:06
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: connections: always register the scheduler  https://review.openstack.org/63744400:37
*** ruffian_sheep has joined #zuul01:17
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: connections: always register the scheduler  https://review.openstack.org/63744401:20
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: connections: remove unused getSchema procedure  https://review.openstack.org/63744501:46
*** sdake has joined #zuul02:00
*** sdake has quit IRC02:18
*** sdake has joined #zuul02:21
*** sdake has quit IRC02:44
ruffian_sheepCan anyone tell me what is the reason? http://paste.openstack.org/show/745241/03:22
ruffian_sheepI can use the cmd :git clone ssh://hjy@review.openstack.org:29418/openstack-dev/sandbox /var/lib/zuul/executor-git/review.openstack.org/openstack-dev/sandbox to clone .03:22
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: fixtures: use default _cleanUp procedure  https://review.openstack.org/63744903:23
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: config: add playbooks to job.toDict()  https://review.openstack.org/62134304:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: Add API endpoint to get frozen jobs  https://review.openstack.org/60707704:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: Get executor job params  https://review.openstack.org/60707804:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: Separate out executor server from runner  https://review.openstack.org/60707904:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: zuul-runner: implement prep-workspace  https://review.openstack.org/60708204:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: web: add /connections route  https://review.openstack.org/63170304:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: zuul-runner: use connections endpoint for prepare-workspace  https://review.openstack.org/63170404:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: zuul-runner: add execute sub-command  https://review.openstack.org/63094404:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: zuul-runner: add support for depends-on  https://review.openstack.org/63206404:37
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: zuul-runner: add quick-start integration test  https://review.openstack.org/63570104:37
ruffian_sheepI meet some probelm can anyone help me ? The log showed me taht git.exc.GitCommandError: Cmd('git') failed due to: exit code(-13)05:55
*** chandankumar is now known as chkumar|ruck06:17
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745806:20
tobiashruffian_sheep: maybe you miss the sshkey config in zuul.conf: https://zuul-ci.org/docs/zuul/admin/drivers/gerrit.html#attr-%3Cgerrit%20connection%3E.sshkey06:21
ruffian_sheeptobiash:T have set it in the zuul.conf. http://paste.openstack.org/show/745241/06:34
*** sdake has joined #zuul06:38
ruffian_sheeptobiash:Just like you answer the baiyi.I can git clone this by myself.But it cannot be cloned in this way.I have checked that I set the ssh public key in https://review.openstack.org/#/settings/ssh-keys .06:40
ruffian_sheeptobiash:I read the log you told with baiyi in the link :eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2017-11-30.log.html06:41
ruffian_sheeptobiash:I also checked the permission of the files.The path /var/lib/zuul/executor-git/ and the file in the document is all belong to zuul:zuul.06:43
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add /connections route  https://review.openstack.org/63170306:46
*** AJaeger has quit IRC06:55
*** AJaeger has joined #zuul07:01
openstackgerritFelix Schmidt proposed openstack-infra/zuul master: Add new merger job to get role definitions from a repository  https://review.openstack.org/63718107:04
*** sanjayu__ has joined #zuul07:17
*** quiquell|off is now known as quiquell|rover07:23
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745807:24
*** sdake has quit IRC07:30
*** quiquell|rover is now known as quiquell|rover|b07:36
*** pcaruana has joined #zuul07:43
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745807:48
*** sshnaidm|off is now known as sshnaidm07:56
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745808:02
*** quiquell|rover|b is now known as quiquell|rovee08:05
*** quiquell|rovee is now known as quiquell|rover08:05
*** panda|off is now known as panda08:09
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745808:12
*** badboy has joined #zuul08:20
*** gtema has joined #zuul08:22
*** themroc has joined #zuul08:23
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745808:43
zbrSpamapS: thanks for the heads on ANSI, let me know if I can help with it. maybe you can share with me an easy way to test/benchmark it.08:47
*** jpena|off is now known as jpena08:52
*** ruffian_sheep has quit IRC08:52
*** pcaruana|afk| has joined #zuul09:01
quiquell|rovertobiash, tristanC: Do you know if zuul will override "files" section if job is run in periodic trigger ?09:02
*** pcaruana has quit IRC09:02
tobiashquiquell|rover: hrm, I guess it won't match09:02
quiquell|rovertobiash: feels like a bug09:03
quiquell|rovertobiash: I suppose periodic has to ignore files09:03
tobiashquiquell|rover: maybe, let's discuss this when corvus is around09:03
quiquell|rovertobiash: going to reproduce09:04
quiquell|roverjpena: ^09:08
quiquell|rovertobiash: files: [] can help workaround this ?09:12
*** sdake has joined #zuul09:14
zbrzuul console uses websockets and does not work behind squid. does anyone knows how to configure squid to make it work?09:15
zbrfor the moment i will just add zuul.openstack.org to the exclude list for proxy config.09:20
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745809:20
openstackgerritSimon Westphahl proposed openstack-infra/zuul master: wip: Jaeger tracing PoC  https://review.openstack.org/63750509:42
openstackgerritSimon Westphahl proposed openstack-infra/nodepool master: wip: Jaeger tracing PoC  https://review.openstack.org/63750609:42
*** electrofelix has joined #zuul09:42
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: amqp: add basic trigger  https://review.openstack.org/63745809:47
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: WIP: Second try to fix single cloud config reload  https://review.openstack.org/60869509:50
*** pcaruana|afk| has quit IRC10:01
*** pcaruana has joined #zuul10:07
openstackgerritJakub Bielecki proposed openstack-infra/nodepool master: doc bugfix for static provider  https://review.openstack.org/63751810:32
openstackgerritFabien Boucher proposed openstack-infra/zuul master: URLTrigger driver time based - artifact change jobs triggering driver  https://review.openstack.org/63556711:05
openstackgerritFabien Boucher proposed openstack-infra/zuul master: URLTrigger driver time based - artifact change jobs triggering driver  https://review.openstack.org/63556711:06
*** hashar has joined #zuul11:12
*** hashar is now known as hasharAway11:12
openstackgerritFabien Boucher proposed openstack-infra/zuul master: URLTrigger driver time based - artifact change jobs triggering driver  https://review.openstack.org/63556711:13
*** sdake has quit IRC11:16
*** sdake has joined #zuul11:20
*** goern has joined #zuul11:31
*** jpena is now known as jpena|brb11:42
quiquell|rovertobiash: confirmed at local zuul12:02
quiquell|rovertobiash: periodic with files does not work12:02
*** sdake has quit IRC12:12
*** sdake has joined #zuul12:16
quiquell|rovertobiash: https://storyboard.openstack.org/#!/story/200504012:26
*** rlandy has joined #zuul12:54
*** jpena|brb is now known as jpena13:27
*** sdake has quit IRC13:28
*** quiquell|rover is now known as quique|rover|eat13:28
*** sdake has joined #zuul13:56
*** quique|rover|eat is now known as quiquell|rover14:09
fungiquiquell|rover: how would you expect a files filter to work with a periodic trigger, out of curiosity?14:23
fungi(files filters are based on the list of files modified by the triggering change, and there is no "change" associated with a periodic trigger)14:23
quiquell|roverfungi: I expect it to run, you can have changes at those same files but comming from RPMs promoted14:24
fungiquiquell|rover: ahh, i see. more generally, should triggers which don't provide a list of files not take the files filters for jobs into account?14:24
quiquell|roverfungi: yep14:25
quiquell|roverfungi: Timer trigger have to ignore files14:25
fungi(as opposed to literally checking to see if any listed files match, which they never will)14:25
fungidoesn't sound like a bug, but does sound like a potentially useful behavior change14:25
quiquell|roverfungi: Yep that's why I send the email, is not a bug since this was not even a feature :-)14:26
*** gtema has quit IRC14:26
fungicool, thanks!14:26
quiquell|roverfungi: If I have a free brain cycle I will try to put some unit test + fix14:27
quiquell|roverfungi: doesn't look to difficult14:27
quiquell|rovers/to/too/14:27
*** chkumar|ruck is now known as chandankumar14:28
odyssey4mehas anyone else seen this pop up? https://gist.github.com/odyssey4me/666909262135edb1aeed37ef548bfe4b - it seems related to nodepool/openstacksdk changes cc mordred14:29
mordredodyssey4me: Proxy object has no attribute servers basically means the sdk failed to create a compute adapter - probably due to issues with discovery - looking real quick14:35
mordredodyssey4me: is this using rax public?14:35
odyssey4memordred yep, rax public cloud serves multiple providers - I can check to see whether this is also happening on a standard openstack cloud14:36
mordredodyssey4me: I mean - it should work - we use rax public for openstack, and I just did a quick test script14:37
*** jkt_ is now known as jkt14:37
odyssey4memordred hmm, well - what's not very handy is that the exception does not provide any information to help me know which provider the node is from, or what request it is... r anything14:40
odyssey4meso I have no way of knowing whether the log is repeating the same error for a single node, or whether it's a bunch of the14:40
odyssey4me*them14:40
mordredodyssey4me: yeah. sorry about that - it's a pretty terrible error message14:41
* mordred is looking for a good way to improve that real quick14:42
pabelangergrr14:51
pabelangerjust hit: https://review.openstack.org/636764/14:51
pabelangersorr14:52
pabelangerhttps://review.openstack.org/637023/14:52
pabelangerwell, the stack at ^14:52
pabelangerI've just +3'd14:52
pabelangerWould not object to a new zuul release this week :)14:53
odyssey4memordred ok, so it seems that I have multiple nodes stuck in a 'deleting' state across multiple public cloud regions - IAD, ORD, LON - some have been stuck for over 15 days :p14:54
mordredodyssey4me: awesome14:55
mordredodyssey4me: I think I have an idea of how to at least make that error suck less14:55
*** sdake has quit IRC14:58
fungiodyssey4me: seems like nova's delete api method is merely a means of indicating that you would appreciate deletion of an instance some day14:59
* fungi has sadly seen this fairly often as well15:00
odyssey4mefungi heh, well, the thing is that nova has never received the request by the looks of things... the state in openstack is active15:00
fungiohh15:00
fungii guess nodepool retrying to delete them doesn't help either since it's probably just repeating the same call15:02
Shrewsall: i was supposed to return today, but i cannot keep my head up due to some horrible illness that has decided to afflict me today. imma go back to bed15:04
mordredodyssey4me: remote:   https://review.openstack.org/637563 Bail earlier on a version mismatch for a supported service15:05
mordredodyssey4me: that won't fix the underlying issue - but it should at least improve error logging to try to find the issue15:05
mordredShrews: go to bed!15:06
mordredodyssey4me: is it possible that nodepool process is running with an older version of keystoneauth loaded?15:06
mordredodyssey4me: we fixed a rackspace issue in 3.11.2 (which your freeze shows you're running)15:07
*** badboy has quit IRC15:07
tobiashcorvus, mordred, fungi: not sure if you got an email notification, maybe you want to have a look at https://storyboard.openstack.org/#!/story/200503715:09
fungiShrews: thanks for the check-in, and hope you get feeling better!15:10
fungitobiash: thanks, i should remember to set up e-mail notification for projects i follow in sb15:10
*** quiquell|rover is now known as quiquell|off15:11
fungitobiash: oh, it's a private story... yeah there's a shortcoming in sb where it doesn't send notifications when private stories are created. corvus tried to start on a fix for it but got stuck on inscrutable test failures. sb's testing needs a severe overhaul15:11
openstackgerritMerged openstack-infra/zuul master: Make UnsafeTag self registering  https://review.openstack.org/63702315:20
fungicorvus: tobiash: dmsimard: on a related note, how do you feel about switching story 2003552 to public? it's been sitting there for nearly 6 months and doesn't describe an actual vulnerability, just a class of potential ones15:21
tobiashI guess we could open it15:23
*** nilashishc has joined #zuul15:24
*** nilashishc has quit IRC15:30
fungithe associated hardening feature in ara was public as of august 2415:38
*** sanjayu__ has quit IRC15:44
*** sdake has joined #zuul15:46
odyssey4memordred possible, although it'd have to be grabbing that through py2 somehow15:46
dmsimardfungi: it can be made public as far as I am concerned15:48
fungithanks dmsimard!15:48
*** jamesmcarthur has joined #zuul16:01
*** iurygregory has joined #zuul16:07
*** pcaruana has quit IRC16:10
jlkclarkb: corvus: did the caching of PR to head SHA go live yet? Have y'all seen any queue improvements?16:31
clarkbjlk: it did and yes, but we discovered an issue with it16:31
jlkoh boy!16:31
jlkwas it the statuses on merged PRs?16:32
clarkbjlk: ansible runs post merge testing and merges create new commits. Our old expiration method was to remove closed PRs from the table16:32
clarkbyup16:32
jlkright, so you get a status event but it's on a closed PR16:32
clarkboverall it seemed to help but we were still getting hit by those post merge statuses so I think new plan is to update to a LRU (with possible time based expiry) cache16:32
clarkbya16:32
jlkyeah, easy enough to mark it as a non-open PR in the cache, but less easy to decide when to purge the cache.16:33
jlkwhat's "LRU" mean?16:33
clarkbleast recently used16:33
clarkbso we'll set some upper bound size and when we hit that in the table evict the entries for the entry that hasn't been used recently compared to the others16:34
*** cognifloyd has joined #zuul16:34
*** themroc has quit IRC16:34
jlkthat seems reasonable, but more complicated code wise16:35
jlkWouldn't it be more fun to just cache unbound, and then award a prize to the event that OOMs the box?16:36
clarkbjlk: the automatic merge event16:38
clarkband ya it is more complicated, I don't think we've started writing the change yet16:39
jlkAt least you know the complexity is worth it, if you're seeing queue improvement already16:39
clarkbya current github queue length is 0, but we still log occurences >0 for largish periods of time, the improvement is we are able to recover unlike before16:40
jlk👍16:41
*** nilashishc has joined #zuul16:42
*** nilashishc has quit IRC16:46
*** panda is now known as panda|off16:58
fungiit's up to 118 as of just now17:00
*** sdake has quit IRC17:00
fungistarted climbing around 15 minutes ago17:00
*** sdake has joined #zuul17:05
odyssey4memordred ok, so I did a little clean up to make sure we're running keystoneauth1==3.11.2 but no dice... if this is all due to version negotation, then perhaps I can just set the version in clouds.yaml and move on with life?17:08
*** gtema has joined #zuul17:08
clarkbfungi: ya it is going to jump anytime ansible merges changes17:22
clarkbfungi: until we get the updated cache behavior implemented17:22
fungiand now up to 172. yeah it does eventually burn back down at least17:23
*** nilashishc has joined #zuul17:30
*** nilashishc has left #zuul17:30
corvusclarkb: want to abandon https://review.openstack.org/636751 ?17:43
clarkbdone17:43
openstackgerritMerged openstack-infra/zuul-jobs master: Update docker image roles  https://review.openstack.org/63738717:51
openstackgerritMerged openstack-infra/zuul master: Add spec for multi ansible version support  https://review.openstack.org/62392717:56
*** gtema has quit IRC17:56
*** jpena is now known as jpena|off18:09
openstackgerritMerged openstack-infra/zuul master: web: prevent status update loop in background  https://review.openstack.org/63634318:18
odyssey4memordred well, I did a pip3 install --upgrade of openstacksdk, which brought some more things to the party, and now all seems well...18:20
odyssey4meI updated the gist with the python packages changes, in case you're interested and may see something18:21
*** sdake_ has joined #zuul18:29
*** sdake has quit IRC18:29
jlkAnecdotally it does appear that Travis right now is not triggering CI on Draft PRs18:34
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Load buildset_registry in intermediate pull  https://review.openstack.org/63760318:48
openstackgerritMerged openstack-infra/zuul master: connections: always register the scheduler  https://review.openstack.org/63744418:54
jktdo you think that it would be reasonable to add a change's sha1 into zuul variables somewhere?18:56
jlk... that's not already there somewhere?18:57
jktmy use case it that I want to cache artifacts, so I would like to add a post-run trusted job which checks if a job has produced ~/artifacts/{{ zuul.project.name }}/$SHA1 , and if it exists, use that18:57
jktso that a malicious job can only poison cache for its own sha118:57
clarkbperhaps under the zuul.projects list? and ya doesn't seem we write that down in the inventory18:57
openstackgerritMerged openstack-infra/zuul master: connections: remove unused getSchema procedure  https://review.openstack.org/63744518:58
jktjlk: it doesn't appear there when I check that variable from inside a check job18:58
jlkhuh. I figured that was like base functionality of a CI system, provide the sha it's working from.18:58
jktit "doesn't have to" because of $magic :), mainly because all correct refs are already set up by the executor18:58
corvusjkt: given your use case, i think the sha may not be sufficient and you may want to take a different approach18:58
jlkjkt: yeah, but I've seen other CI systems provide it as an ENV variable in the execution environment.19:00
corvusjlk: remember that the thing zuul is testing may not exist, it may be N changes across Y projects in the future.  we could provide the sha of the most recent commit in that change (the sha of the change under test) but that may not be what's checked out.  because of that, so far, it hasn't been a useful thing to add to the inventory.19:00
jlkI just _assumed_ that Zuul did the same.19:00
corvusjkt: are you familiar with the work i'm doing on container artifact caching?19:00
jktcorvus: I am not19:00
corvusjkt: let me dig up some stuff19:00
openstackgerritClark Boylan proposed openstack-infra/zuul master: Rename project to project_name in getPullBySha  https://review.openstack.org/63721819:01
openstackgerritClark Boylan proposed openstack-infra/zuul master: Test GithubShaCache  https://review.openstack.org/63722819:01
clarkbcorvus: tobiash ^ addressed your comments re project_name19:01
jktcorvus: okay, I know that it could be a transient merge, fair enough19:01
jlkcorvus: right, I think it would be more useful on post-merge jobs, like "now that you've tested and merged this thing, run a job to build an artifact and upload it somewhere"19:01
corvusjlk: in the case of a post-merge event, the sha is provided19:02
corvusjkt: here's an email i wrote which describes it -- http://lists.zuul-ci.org/pipermail/zuul-discuss/2019-January/000718.html19:02
jktI'm doing this for a repo which essentially only contains (as git submodules) references to other git repos, repos that I cannot gate on because they are from an external project from github19:02
* jkt reads19:02
corvusjkt: (we're going with alternative #2, ftr)19:03
corvusjkt: basically, with the combination of provides/requires and zuul artifacts, you can get artifacts built for a previous change in a patch series.19:04
corvus(so you get speculative artifacts via git commit parents, and depends-on footers)19:04
jktyeah, the artifacts and provides/requires, I asked about these last week19:07
jktwhat I figured that I could use "now" is a simple logic driven by the git commit hash of the repo which provides these images/artifacts19:08
corvusjkt: oh, sorry, all of the stuff in zuul to support this has landed19:08
corvusthe only thing i'm still working on is the roles to do this for a docker registry19:08
jktyup, if the version which ends up getting commited is different (perhaps due to gerrit and zuul merging in a different way, or producing a commit with a different date etc), there would be a cache miss19:09
jktI'm still not that fluent with Ansible, and my zuul server is centos7 without all these deps for a JS/webapp build, so I sticked with a release of Zuul so far, but that's not a big deal19:10
corvusoh, ok.  it'll probably be either later this week or early next before we do a release with this, mostly because i at least want to see it proven to work once before we do so, to make sure we haven't missed anything :)19:10
jktI wanted to go with just copying the artifacts somewhere, similarly to a log server, but not actually prefixed by the usual change number prefix19:10
jktso that I have a repo which consumes these artifacts, and I could just wget foo/{{ zuul.job }}/{{ zuul.projects.THAT_SUBMODULE.sha1 }}/deps.tar19:11
corvushttps://zuul-ci.org/docs/zuul-jobs/roles.html#role-pull-from-intermediate-registry  and  https://zuul-ci.org/docs/zuul-jobs/roles.html#role-push-to-intermediate-registry are the roles that implement the push/pull using artifacts19:12
jktyeah, it indeed sounds like an interesting feature -- it's just that for me, this is not docker, so I will have to provision a custom registry and what not19:13
jktcompared to that, a predictable name of the artifact and a simple wget is much, much easier IMHO19:13
corvusit should work with a static fileserver too19:13
corvusjkt: yeah, this is totally doable with a simple wget :)19:13
jktthere is also one more build when a change is merged19:14
corvusjkt: if you also hook in a "promote" pipeline, so that deps.tar gets promoted to a known location on each merge, then your "pull" role becomes "is there a deps.tar artifact variable set due to provides/requires? if so, pull from its url.  if not, pull from the standard location"19:14
corvusjkt: exactly, yes, that's the promote part.19:14
jktcorvus: but how do I access the original change from promote?19:14
corvusjkt: but you don't have to make another build in that case19:15
*** electrofelix has quit IRC19:15
jkttrying ot understand that19:15
corvusjkt: you can have your gate pipeline push its intermediate build to a location that's keyed based on the change, and then have the promote job pull from there and push to the publication url19:15
corvusjkt: the example i have for that (again, for docker images) is https://zuul-ci.org/docs/zuul-jobs/roles.html#role-upload-docker-image and https://zuul-ci.org/docs/zuul-jobs/roles.html#role-promote-docker-image19:16
jktcorvus: do you have an example of a promote job which does that, and showing the interaction between gate and promote? I digged through some real-world jobs visible at openstack's zuul status dashboard19:17
jktbut I got lost in all these indirections19:17
corvusjkt: yes, we're using the promote stuff in production now (we're building in gate, and publishing in promote).  the zuul docker image build jobs use that19:17
jkt(these were not using provides/requires, sure, just release tarballs, but I got lost nonetheless)19:17
corvusonly the docker images are using promote right now, no one has backported tarballs to it yet19:18
*** jamesmcarthur has quit IRC19:19
jktcorvus: I thought that "promote" is a fully independent pipeline which only has access to the state of the repo, not to a gate job which "caused" it19:20
corvusjkt: unlike our "post" pipeline, "promote" is triggered by a change-merged event, so it has the change which "caused" it available, but not the resulting commit sha.19:21
jktah, doh!19:21
jktthanks, that looks like that missing piece19:21
corvusjkt: so it's not suitable for building an artifact where it needs to be tracable to the underlying commit sha (because it will have used zuul's speculative sha, not the real one that landed).  but if you don't need that, it's okay.19:22
corvusi think it's good enough for our (openstack and zuul) docker images and documentation builds at least.  openstack may want to continue to build its tarballs post-merge depending on considerations like gpg signing, etc.19:23
jktto be honest, I have not been using "gate" so far -- "check" was enough for me. This obviously requires "gate", but that's not really a problem19:23
jkt(apart from that extra Workflow label :) )19:23
corvusyeah, this depends on being sure that something landed, and that what landed was exactly what was tested/produced19:24
jktcorvus: where do I see this promote thing in action? I grepped zuul-jobs and openstack-infra/project-config, but it seems like something that might be getting used from project's own .zuul.yaml, perhaps?19:27
jktcorvus: okay, I found and example in Zuul's own zuul.yaml :)19:29
jktcorvus: thanks for this, I'll take a deeper look into this and ask tomorrow if there are any more missing pieces19:30
*** jamesmcarthur has joined #zuul19:33
openstackgerritClark Boylan proposed openstack-infra/zuul master: Switch to LRU + TTL based sha to PR cache  https://review.openstack.org/63761519:40
clarkbcorvus: tobiash jlk ^ first pass at switching to LRU + TTL based cache. Hopefully the test suite makes it easy to see that this works :)19:41
openstackgerritMerged openstack-infra/zuul-jobs master: Load buildset_registry in intermediate pull  https://review.openstack.org/63760319:43
clarkbfwiw cachetools is MIT licensed, relatively small and well written so I don't think we should try and write our own version of an LRU ttl based cache19:43
clarkbSpamapS: ^ you were interested in this too I think re caches19:45
clarkbI don't know if 3 hours is long enough fwiw. I figured we could tune that in review19:46
corvusclarkb: why lru+ttl?  why not just lru?19:47
corvusi feel like ttl is basically "try to guess how long jobs run"19:47
clarkbcorvus: spamaps was concerned we'd go stale in the multi commit case iirc19:48
clarkber one sha to many PRs case? because we'd cache the first then enver add others19:48
clarkbI suppose that behavior may actually be better for zuul since it doesn't know how to handle multiples19:48
corvusi thought i responded to that in a way which i thought addressed the concern19:48
clarkboh I missed it if so19:49
clarkbits a simple change to switch to an LRU. Basically have to update the cache type and update the test for removal19:49
corvusi guess i will go dig it up and copy it into my review :(19:49
*** sdake_ has quit IRC19:54
openstackgerritClark Boylan proposed openstack-infra/zuul master: Switch to LRU based sha to PR cache  https://review.openstack.org/63761519:59
clarkbthat is an LRU version19:59
*** cognifloyd has quit IRC20:00
SpamapSYeah I believe corvus addressed that.20:17
SpamapSWhen we were talking it through I came to the conclusion that LRU and the update-from-events should be plenty.20:17
SpamapS(I think anyway)20:18
clarkbin any case both version are pushed now (with LRU being latest patchset) and the test suite is useful for that transition even with minor tweaks to handle the behavior change20:19
*** hasharAway has quit IRC21:31
*** hasharAway has joined #zuul21:31
clarkbanyone willing to give the lru cache stack at https://review.openstack.org/637615 a look? Mostly wondering if people like the approach (and if so maybe we can get it in soon?)21:49
*** sdake has joined #zuul22:32
*** sdake has quit IRC22:46
*** sdake has joined #zuul22:49
corvusclarkb: do you want to give https://review.openstack.org/636705 another look?23:07
clarkblooks like just a rebase for the cache addition?23:08
clarkbI've approved it23:08
corvusclarkb: i'm +2 on your whole cache stack23:11
clarkbthanks23:11
*** sdake has quit IRC23:24
*** sdake has joined #zuul23:24
*** sdake has quit IRC23:32
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Fix build-docker-image when using buildset_registry  https://review.openstack.org/63765023:33
openstackgerritMerged openstack-infra/zuul master: Re-use the github PR object when fetching reviews  https://review.openstack.org/63670523:36
openstackgerritMerged openstack-infra/zuul master: Add comment about extra issues request  https://review.openstack.org/63670623:36
openstackgerritClark Boylan proposed openstack-infra/zuul master: Don't request PR issue data  https://review.openstack.org/63672823:40
openstackgerritClark Boylan proposed openstack-infra/zuul master: Don't request PR issue data  https://review.openstack.org/63672823:41
clarkbI think I managed to push the rebase clean then fix what I think is the issue (though the tests may still be broken)23:42
*** spsurya has quit IRC23:58

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