Monday, 2020-05-11

fungieasy enough to check...00:21
fungisurvey says... nope: https://packages.ubuntu.com/focal/python3-pip00:21
ianwok, yeah it's that we list it in the packages to install when we take that path00:22
fungipython3-pip and python3.8-venv both depend on python-pip-whl which provides an unpackable wheel copy of pip00:23
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] fix venv  https://review.opendev.org/72670400:24
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Revert "ensure-tox: use venv to install""  https://review.opendev.org/72670500:24
fungii think python3-pip winds up bouncing through ensure-pip to unpack the contents of python-pip-whl into the system context, while the venv module unpacks the same into any venv it creates00:24
fungimmm, i guess not on the first supposition... python3-pip actually includes pip directly: https://packages.ubuntu.com/focal/all/python3-pip/filelist00:26
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] fix venv  https://review.opendev.org/72670400:29
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Revert "ensure-tox: use venv to install""  https://review.opendev.org/72670500:29
ianwok, that passes and i think is the solution, let clean it up00:39
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip: always check for python3-venv on Debuntu  https://review.opendev.org/72670400:44
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Revert "ensure-tox: use venv to install""  https://review.opendev.org/72670500:44
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] venv probe full path  https://review.opendev.org/72671501:00
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip: always check for python3-venv on Debuntu  https://review.opendev.org/72670401:10
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Revert "ensure-tox: use venv to install""  https://review.opendev.org/72670501:10
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] venv probe full path  https://review.opendev.org/72671501:10
*** swest has quit IRC01:47
*** swest has joined #zuul02:02
*** cloudnull2 has joined #zuul02:15
*** cloudnull has quit IRC02:16
*** cloudnull2 is now known as cloudnull02:16
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip: use full python3 path  https://review.opendev.org/72671503:17
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip: use full python3 path  https://review.opendev.org/72671503:40
*** evrardjp has quit IRC04:36
*** evrardjp has joined #zuul04:36
AJaegerthanks, ianw ! Will review later...05:17
AJaegerianw: this is all about python3 - is the python2 package fine or do we need to do anything there as well?05:55
ianwAJaeger: this is really just about what we're exporting as the tool to install venv's, which should just be "python3 -m venv" as every platform has that06:02
AJaegerianw: Thanks, Understood now. I double checked that py27 env uses py27 as well06:03
ianwyeah, the *tox* should be fine installed in a python3 venv, and it can then run with python206:05
ianwlike as in -e py2706:05
*** dpawlik has joined #zuul06:10
AJaegeryep, that worked06:10
*** dpawlik has quit IRC06:13
*** yolanda has joined #zuul06:18
*** dpawlik has joined #zuul06:18
*** saneax has joined #zuul06:31
*** fbo|off is now known as fbo|afk06:55
*** jcapitao has joined #zuul07:10
*** tosky has joined #zuul07:34
*** rpittau|afk is now known as rpittau07:36
*** hashar has joined #zuul07:38
*** avass has joined #zuul07:42
*** jpena|off is now known as jpena07:53
*** panda|pto is now known as panda08:04
*** arxcruz has quit IRC08:10
*** arxcruz has joined #zuul08:10
*** Miouge- has joined #zuul08:15
*** EmilienM has quit IRC08:15
*** Miouge has quit IRC08:15
*** SpamapS has quit IRC08:15
*** SpamapS has joined #zuul08:16
*** EmilienM has joined #zuul08:16
*** sshnaidm|off is now known as sshnaidm09:15
openstackgerritAlbin Vass proposed zuul/zuul master: Enables whitelisting and configuring callbacks  https://review.opendev.org/71726009:16
openstackgerritAlbin Vass proposed zuul/zuul master: Enables whitelisting and configuring callbacks  https://review.opendev.org/71726009:18
avasstobiash: how about that?09:18
*** pingou has joined #zuul09:35
*** nils has joined #zuul09:36
* pingou waives to nils09:36
* nils waves back09:36
nilsI just asked about testing Zuul jobs over on #fedora-ci -- I want to test a job I'm developing locally i.e. before committing it to the repo.09:39
nilsJust to see if I use the right macros/variables and if my playbook works and so on.09:40
nilsAnd the only thing I found re: doing this would be to follow the quick-start installation and tutorial and spin up the whole thing locally, only it doesn't seem to work (this is with SELinux not enforcing, just in case): https://paste.centos.org/view/e7ee440409:42
nilsDoes anybody around have an idea what's going wrong? Or is there a lighter-weight way how I can test my job?09:42
avassnils: you could test the playbooks and roles by running ansible, but you would need a zuul to test the job config as far as I know10:06
nilsthanks10:07
avassnils: but if you're using any zuul: vars you need to mock them away, you can do that by passing an extra-vars file10:09
avassnils: you could do something like this: https://review.opendev.org/gitweb?p=zuul/zuul-jobs.git;a=blob;f=test-playbooks/artifactory/run.yaml;h=08050d80b0f852c92747e607e6a76d64d4c3b37c;hb=7004f0328b2b30fc76f2dba7778ccf8cfd551c57#l6410:11
nilsavass, the zuul vars are part of what I wanted to test ;) because it's the first custom job I'm writing10:12
avassnils: ah :)10:12
nilsbut I guess I can ask here :)10:12
nilsSo, if I wanted to do something with the diff of a pull request, would zuul.branch as the "base" of the diff and zuul.change as the "tip" be the right variables to use?10:14
nilsThe difference between zuul.change and zuul.patchset isn't obvious when reading https://zuul-ci.org/docs/zuul/reference/jobs.html#change-items10:14
nilsI assume one of the identifies the pull request and the other the tip of the feature branch being submitted, but I'm not sure which is which.10:15
*** rpittau is now known as rpittau|bbl10:15
avassnils: hmm, I don't know how zuul.patchset behaves for something other than gerrit10:16
nilsavass, I assume that the "change items" variables are the place to look for this information, though, would that be right?10:17
nilsGettting more concrete, I want to pipe the diff of a submitted PR through ansible-review (because ansible-review on the whole repo takes ages and there might be broken stuff in it anyway). I need the branch point (which would be the tip of the branch the PR is submitted agains) and the tip of the PR (branch).10:18
avassnils: looks like the patchset for github is the sha of HEAD on the PR10:20
nilsThat's great info, thanks again!10:20
avassand zuul.branch is the branch being targeted e.g master in most cases10:21
avassI think10:22
avassnils: no problem :)10:22
nilsavass, yeah that would let me do `git diff {{ zuul.branch }}..{{ zuul.patchset }} | ansible-review ...`10:24
avassyeah :)10:24
nilsAhh maybe rather `git diff $(git merge-base {{ zuul.branch }} {{ zuul.patchset }})..{{ zuul.patchset }}` :D10:24
nilsNot sure if this is the same as `... { zuul.branch }...{ zuul.patchset } ...`10:26
avassnils: wouldn't that produce the same output?10:26
*** jcapitao is now known as jcapitao_lunch10:27
nilsIf say master has moved on in the meantime, then the diff isn't meaningful10:27
nilsI'm not sure if three dots achieve the same with git diff as computing the merge base manually10:27
avassnils: ah, but you'd want to diff against the head of master right? git diff $(git rev-parse {{ zuul.branch }}) {{ zuul.patchset }}10:29
nilsavass, only if the head of master is the merge base, too :)10:30
nilssince git diff can cope with branch names I don't have to use git rev-parse I guess10:30
avassah yeah, heh10:31
avasszuul-jobs-maint: can you take a look at https://review.opendev.org/#/c/690057/10:57
*** fbo|afk is now known as fbo11:06
*** iurygregory has quit IRC11:37
*** jpena is now known as jpena|lunch11:37
*** pingou has left #zuul11:42
*** jcapitao_lunch is now known as jcapitao11:42
*** toabctl has quit IRC11:43
*** rfolco has joined #zuul11:53
*** rfolco is now known as rfolco|rover11:53
*** rpittau|bbl is now known as rpittau11:58
*** iurygregory has joined #zuul11:58
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Remove requiring tox_envlist  https://review.opendev.org/72682912:19
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Deprecate default tox_envlist: venv  https://review.opendev.org/72683012:20
*** rlandy has joined #zuul12:22
avasszuul-jobs-maint: I think the default behaviour of defaulting to venv in the tox role is a bit unintuitive, can we deprecate that?12:23
*** jpena|lunch is now known as jpena12:33
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Remove requiring tox_envlist  https://review.opendev.org/72682912:35
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Deprecate default tox_envlist: venv  https://review.opendev.org/72683012:36
AJaegermordred, mnaser , please review this stack: https://review.opendev.org/#/c/72670412:37
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Do not fail if stestr or testr is not found  https://review.opendev.org/72683612:46
*** zxiiro has joined #zuul12:57
*** sgw has joined #zuul12:58
*** iurygregory has quit IRC13:01
avassmordred: why do we run tox here: https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/tox/tasks/siblings.yaml#L1 ?13:02
*** iurygregory has joined #zuul13:02
AJaegeravass: to install all requirements - and then we replace the "siblings"13:03
avassAJaeger: ah13:03
avassAJaeger: that probably needs a comment13:04
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Deprecate default tox_envlist: venv  https://review.opendev.org/72683013:10
AJaegeravass: let's double check that with mordred13:10
avassAJaeger: if you have time, want to take a look at the upload-artifactory role? :) https://review.opendev.org/#/c/725678/13:15
AJaegeravass: will try later today13:16
avassAJaeger: thanks!13:16
*** nhicher has quit IRC13:19
*** fbo has quit IRC13:19
openstackgerritMerged zuul/zuul-jobs master: ensure-pip: always check for python3-venv on Debuntu  https://review.opendev.org/72670413:20
*** Goneri has joined #zuul13:21
*** Defolos has joined #zuul13:25
*** fbo has joined #zuul13:27
*** nhicher has joined #zuul13:28
mordredAJaeger, avass yes - that's right13:29
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add explanatory comment to tox siblings  https://review.opendev.org/72684513:32
avassmordred: ^ :)13:32
*** dpawlik has quit IRC13:38
*** dpawlik has joined #zuul13:42
funginils: avass: there's this series of changes which hope to separate out a "runner" which could be used to locally (re)execute a zuul job without all the zuul daemons... still, it's a bit like saying you want to test a shell scrip without using the shell to do it, zuul not only supplies variables from the triggering context but also compiles playbooks and roles from a limitless pool of different git repositories,13:58
fungiexpects that changes being tested could depend on other proposed changes which could themselves even contain changes or addition to job configuration, and so on13:58
nilsfungi, that's great to hear and I understand that "running Zuul without Zuul" isn't the same thing. But I imagine that it would allow people to catch a couple of mistakes locally before submitting their changes.14:00
avassfungi: how's that going? I thought there was just a spec for it so far14:00
nilsAlso, a shell is slightly smaller (and easier to get running from scratch) than Zuul :)14:01
nilsNot sure what exactly is going wrong on my end, but I don't seem to be lucky trying it here.14:02
funginils: yep, it was an imperfect analogy14:02
openstackgerritMonty Taylor proposed zuul/zuul-website master: Switch website to Gatsby  https://review.opendev.org/71737114:02
openstackgerritMonty Taylor proposed zuul/zuul-website master: Add blog to website  https://review.opendev.org/72464814:02
nilsfungi, no worries, my comment was in jest14:02
fungiavass: the changes for that review topic are in merge conflict since mid-last year, though there's movement on the spec: https://review.opendev.org/68127714:04
*** tumble has joined #zuul14:05
*** cdearborn has joined #zuul14:09
avassfungi: oh, nice :)14:17
tobiashtristanC: I added a question to the zuul-runner spec14:35
*** jhesketh has quit IRC14:35
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: WIP: Remove requiring tox_envlist  https://review.opendev.org/72682914:42
openstackgerritMerged zuul/zuul-jobs master: Add explanatory comment to tox siblings  https://review.opendev.org/72684514:46
corvusnils: it's also worth noting that since zuul's configuration is dynamically evaluated, you can 'test' the job by pushing up a change that implements it.  you can revise that change until it works as expected, all before merging it.14:53
corvusnils: for determining the "diff", the best way to do that may be "diff origin/{{zuul.branch}} {{zuul.branch}}"14:53
corvusnils: see the discussion at https://zuul-ci.org/docs/zuul/reference/jobs.html#git-repositories for an explanation about that14:54
corvusnils: (2nd paragraph)14:54
corvusnils: i would not recommend zuul.patchset for that -- it may not represent the actual state of the repo after any merges14:55
*** sshnaidm is now known as sshnaidm|afk14:57
*** klindgren_ has joined #zuul15:09
*** klindgren has quit IRC15:09
-openstackstatus- NOTICE: Our CI mirrors in OVH BHS1 and GRA1 regions were offline between 12:55 and 14:35 UTC, any failures there due to unreachable mirrors can safely be rechecked15:09
*** hashar has quit IRC15:14
zbrcorvus: fungi: any change to look at https://review.opendev.org/#/c/690057/ ?15:18
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Add new non-npm specific javascript jobs  https://review.opendev.org/72654715:22
nilscorvus, aah, what's zuul.patchset then?15:24
tristanCtobiash: thanks, just replied15:25
nilsAlso, what do you think of "diff origin/{{ zuul.branch }} {{ zuul.branch }}" vs. "diff origin/{{ zuul.branch }}...{{ zuul.branch }}"?15:25
openstackgerritMerged zuul/zuul-jobs master: Revert "Revert "ensure-tox: use venv to install""  https://review.opendev.org/72670515:29
openstackgerritMerged zuul/zuul-jobs master: ensure-pip: use full python3 path  https://review.opendev.org/72671515:29
corvusnils: zuul.patchset is just informative; it's use is mainly to see what version of a change or pr was tested.  and i'm not really sure about the difference between " " and "..." in git diff15:37
nilscorvus, "diff ref1 ref2" or "diff ref1..ref2" is just the plain diff between two trees, "diff ref1...ref2" is the diff between the merge point of both and ref2, it's equivalent to "diff $(git merge-base ref1 ref2) ref2"15:39
AJaegermordred: I updated your change https://review.opendev.org/726547 - is that ready for review now?15:41
*** kmalloc has joined #zuul15:41
corvusnils: ah.  zuul is going to make "origin/{{zuul.branch}}" be the 'previous state' -- where that might either be the current actual tip of the branch, or, in the case of dependent changes, it could be the resulting speculative merge of the dependent change(s).  then "{{zuul.branch}}" or HEAD is going to be the merge of the current change onto that.  if it's fast-forwardable, it'll be a ff, otherwise it'll be15:44
corvusa new merge commit.  origin/{{zuul.branch}} should always be a parent of {{zuul.branch}}, so i think the commands should be identical in this case.15:44
clarkbnils: I think they will be the same in the zuul context due to how zuul works15:44
clarkbcorvus: yup that is my understanding too15:44
corvusclarkb: whew :)15:44
mordredAJaeger: yes - I believe it is - you can see it working here: https://review.opendev.org/#/c/726554/15:45
mordredAJaeger: oh - actually - I think it wants one more little update15:49
mordredAJaeger: no - nevermind. that one is good15:49
nilscorvus, clarkb: thanks, I'll do it "by the book" nonetheless :)15:50
openstackgerritMonty Taylor proposed zuul/zuul master: Update node to v14 and reorg the jobs a bit  https://review.opendev.org/72655315:50
clarkbmordred: AJaeger re ^ yall might have input on the horizon testing threads taht popped up over the weekend?15:51
avasscorvus, nils: Oh right, I should have thought of the speculative merging going on in zuul15:51
mordredclarkb: actually - with the new set of jobs we've got there - we should be able to not install yarn when it's not needed15:52
mordredclarkb: and then we can have horizon migrate to those15:52
mordredlet me respond15:53
clarkbmordred: thanks!15:53
mordredAJaeger: with that - let me update those jobs to handle not installing yarn15:55
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Add new non-npm specific javascript jobs  https://review.opendev.org/72654716:01
AJaegermordred: sorry, just pushed one fix - back over to you ^16:02
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Add new non-npm specific javascript jobs  https://review.opendev.org/72654716:02
mordredAJaeger: crap. didn't see that. let me grab your fix16:02
AJaegermordred: I didn't see IRC ;)16:02
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Add new non-npm specific javascript jobs  https://review.opendev.org/72654716:03
mordredAJaeger, clarkb, yoctozepto: ok. that should be good ^^16:03
yoctozeptomordred: ack, looks fine to my eye16:04
yoctozeptotrying out in jslib16:04
yoctozeptoI should really find some time to push that unlucky thingy16:04
yoctozeptoI am not really sure it will pick those job amendments though16:04
*** tumble has quit IRC16:08
AJaegermordred: LGTM, hope it passes all tests ;)16:08
*** rpittau is now known as rpittau|afk16:09
*** ianychoi_ is now known as ianychoi16:09
tobiashmnaser: do you run the swift proxy we talked about a few months ago?16:09
mnasertobiash: i never got around completing it :(16:10
tobiashah ok16:10
tobiashours broke after an update to python 3.8 because eventlet needs pyopenssl or it breaks openstacksdk16:11
tobiashhttps://github.com/eventlet/eventlet/issues/526 in case someone suffers from "wrap_socket() got an unexpected keyword argument '_context'"16:11
avassmordred, AJaeger: Don't we need to install npm if we don't install yarn? :)16:13
avassor am I just missing that?16:13
mordredavass: hrm. oh - good point! we were counting on ensure-yarn to ensure npm16:13
mordredavass: or - maybe we get npm from node in the first place?16:15
avassmordred: but we install node in ensure-yarn, so if we skip ensure-yarn we need to run ensure-nodejs at least16:16
mordredavass: yeah16:17
mnaserwhat do we think about renaming opendev-buildset-registry (or $site-buildset-registry) to 'base-buildset-registry' -- the reason i ask is because https://zuul.vexxhost.dev/t/opendev/config-errors -- unless i create a fake 'opendev-buildset-registry' job... i'll always have that config error16:17
mnaseri could technically _not_ load any jobs at all, but as i'm only running tox-* jobs, but, that means potentially missing out on adding jobs from zuul-jobs later16:18
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Add new non-npm specific javascript jobs  https://review.opendev.org/72654716:18
openstackgerritMerged zuul/zuul-jobs master: cabal-test: add build target job variable  https://review.opendev.org/72626616:20
openstackgerritMerged zuul/zuul-jobs master: haskell-stack-test: add build target job variable  https://review.opendev.org/72626716:20
avassmordred: lgtm, except for the linting16:20
mordredavass: doh16:20
*** jcapitao has quit IRC16:22
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: tox: allow tox to be upgraded  https://review.opendev.org/69005716:25
avasszbr: rebase that for you ^16:25
avasszbr: uhm, nevermind I'll fix it16:26
zbrthanks!16:28
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Add new non-npm specific javascript jobs  https://review.opendev.org/72654716:30
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Extract ensure-javascript-build-tool role  https://review.opendev.org/72690016:30
mordredavass, zbr: let's make sure ianw looks at that when he's up before we land it - he's been doing a bunch of work updating the tox roles and is juggling a lot of things has all of the things paged in (it doens't look like a problem to me - but I think we should run it by ianw)16:31
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: tox: allow tox to be upgraded  https://review.opendev.org/69005716:32
avassmordred, zbr: sure16:33
avasszbr: that should be alright right?16:33
avasszbr: I'll leave it to you now16:33
zbrfungi: any idea about a better name for tox_constraint variable?16:34
*** evrardjp has quit IRC16:36
avasszbr: tox_required_version?16:36
fungitox_requirements or tox_packages or tox_versions maybe?16:36
*** evrardjp has joined #zuul16:36
avassor that16:36
fungizbr: and as for my comment about the tox-venv plugin, i don't have anything against the plugin personally (and i make extensive use of it in some of my projects), but it seems unrelated to the rest of the change and isn't mentioned in the commit message at all16:39
fungiand it could introduce subtle behavior changes16:40
fungi(though hopefully not, it still deserves its own discussion)16:40
avassfungi: that's just the test-playbook though :(16:41
avass:)*16:42
fungioh, yep, i missed the test- on the front of that directory name16:43
fungisorry about that16:43
yoctozeptomordred: honestly I don't think nodejs-test-dependencies should even install chromium ;-)16:46
yoctozeptothis is only because some of these javascript project target browsers16:46
mordredyoctozepto: ah - nod16:46
yoctozeptoI installed firefox because the original legacy jobs used them16:46
zbri will put "tox_requirements" describes it better.16:46
yoctozeptoif zuul picked the depends-on correctly, then it seems unit tests still pass :-)16:47
yoctozeptousing the new-old jobs16:47
yoctozeptonow could use using the new ones16:48
yoctozeptoit actually relies on nodejs8-jobs template to pull these in16:49
yoctozeptomordred: are you planning updating those templates too?16:49
mordredyoctozepto: also - check my followup patch in https://review.opendev.org/726900 - there's a noteworthy change - which is not installing  dependencies in pre but actually installing them in during run16:49
mordredyoctozepto: I was planning on talking with folks about it - I think we want to make sure updating them doesn't bork people16:50
mordredbut I think it would be a good idea to16:50
zbravass: if you have time look at https://github.com/ansible/ansible-lint/pull/781 as it fixes one error I seen running on zuul-jobs.16:51
yoctozeptomordred: I could then depend on it and see if it breaks these precious unit tests16:51
yoctozeptomordred: aye, why the change though? does pre have more magic than being retried?16:53
mordredyoctozepto: just the retries - but the idea is that pre is setup and shouldn't really ever fail in normal dev workflow, only in environmentally weird cases like an apt repo being unreachable. but devs write patches to add deps all the time - so it's not really appropriate to have a job fail in pre because of that dev action16:56
yoctozeptomordred: ack, good practice to remember, tradeoff of shorts but makes sense, thanks16:57
mordred++16:58
openstackgerritSorin Sbarnea (zbr) proposed zuul/zuul-jobs master: tox: allow tox to be upgraded  https://review.opendev.org/69005716:58
corvusmordred, yoctozepto: yeah, that matches what we do with tox (install python and tox in pre; install project deps in run)16:59
yoctozeptocorvus, mordred: well, that is because it is tox that actually does it in the first place :-)17:02
yoctozeptocorvus, mordred: but yeah, analogy accepted17:02
corvusyoctozepto: (we could have put tox --notests in the pre playbook but did not)17:03
yoctozeptocorvus: fair enough :-)17:03
avasszbr: lgtm17:07
openstackgerritSorin Sbarnea (zbr) proposed zuul/zuul-jobs master: yamlint: EOF newlines and comments indent  https://review.opendev.org/72551617:12
*** sshnaidm|afk is now known as sshnaidm17:12
openstackgerritTristan Cacqueray proposed zuul/zuul master: spec: add a zuul-runner cli  https://review.opendev.org/68127717:18
openstackgerritSorin Sbarnea (zbr) proposed zuul/zuul-jobs master: tox: allow tox to be upgraded  https://review.opendev.org/69005717:20
*** jpena is now known as jpena|off17:25
clarkbmnaser: mordred I sent http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014809.html to openstack-discuss to mention the tox behavior that came up over the weekend17:35
clarkbdo you think it would be helpful to also send that to the zuul-discuss list?17:36
fboHi zuul-maints, I'd like to know if that Ansible plugin dir adjacent to playbook error is expected there: https://pagure.io/fedora-infra/ansible/pull-request/5417:37
clarkbfbo: my understanding is that plugins are not "safe" from a security standpoint so cannot be loaded in an untrusted (or pre merge context)17:38
clarkbfbo: this means you need to ship them in trusted repos17:38
fboclarkb: plugins are in the root of the project but zuul job playbook in ci/ so I'm not sure about that adjacent rule.https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L161017:41
clarkbfbo: its not the adjacency its them existing at all I think17:42
fbothat's unfortunate that this project structure prevent the repo to handled speculatively17:42
tristanCiiuc the plugins are not necessary for zuul, it seems like the check may be too restrictives17:42
clarkboh I see you are saying those plugins exist for ansible and not zuul + ansible17:42
clarkbso zuul should just ignore them?17:42
fungioh, it's plugins shipped in a repository but which zuul isn't expected to use?17:42
tristanCfungi: clarkb: yes, we would like zuul to ignore them17:43
fungii wonder if that can be excluded in the project entry for the tenant17:43
clarkbgot it, in that case I think the issue is going to be related to paths and how zuul/ansible looks for things like playbooks and plugins17:43
fbofungi: yes I guess17:43
clarkbfungi: I think this is controlled more by ansible than zuul17:43
fungioh17:43
clarkbits going to depend on whether or not ansible can be told to ignore those plugins when running under zuul17:44
clarkb(I don't know what the existing behavior does, in theory those plugins would be loaded as is today otherwise we wouldn't be guarding against it)17:44
*** sanjayu_ has joined #zuul17:45
*** saneax has quit IRC17:48
*** fbo is now known as fbo|off17:52
fungimaybe it can be given a pluginpath override17:56
fungior some such17:56
* fungi makes vague hand-waving gesture17:56
avassfungi: maybe have a playbook directory that can't be loaded by zuul?18:08
*** iurygregory has quit IRC18:25
AJaegermordred: could you check my comment at https://review.opendev.org/#/c/726547/13/playbooks/javascript/pre.yaml ?18:27
corvusfbo|off, tristanC, nils: i agree it seems like zuul should only be looking under the ci/ directory, but it seems to be checking the root of the repo; at first glance that seems unexpected and i think it's worth further inspection to understand it.18:28
nilscorvus, I'll look into it tomorrow18:33
*** iurygregory has joined #zuul18:38
avassAJaeger: yeah that should be ensure-nodejs, good catch18:40
*** toabctl has joined #zuul18:57
openstackgerritSorin Sbarnea (zbr) proposed zuul/zuul-jobs master: tox: allow tox to be upgraded  https://review.opendev.org/69005718:59
zbranyone aware of TypeError: unsupported operand type(s) for -=: 'Retry' and 'int' -- pip/urlib3? https://zuul.opendev.org/t/zuul/build/abcad91f4b044b12a695f6bdcab7b88b19:23
zbrthis error loks quite weird, two nested exceptions19:23
AJaegerzbr, earlier error was "http.client.RemoteDisconnected: Remote end closed connection without response19:26
AJaegerzbr: so a not handled timeout?19:26
zbrand apparently nobody cared to fix that bug in pip, i see >2yr bugs with same behavior.19:27
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Add new non-npm specific javascript jobs  https://review.opendev.org/72654719:29
AJaegeravass: thanks. fixed it ^19:30
*** kmalloc has quit IRC19:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Extract ensure-javascript-build-tool role  https://review.opendev.org/72690019:33
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Extract ensure-javascript-build-tool role  https://review.opendev.org/72690019:35
*** nils has quit IRC19:51
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Extract ensure-javascript-build-tool role  https://review.opendev.org/72690019:56
mordredAJaeger: ++ thank you!20:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Extract ensure-javascript-build-tool role  https://review.opendev.org/72690020:05
AJaegermordred: fixed one more problem ^20:05
AJaegermordred: testing in https://review.opendev.org/#/c/726940/120:06
AJaegermordred: could you review my changes, please? - and take over again? I'm signing off now...20:07
*** avass has quit IRC20:08
*** dpawlik has quit IRC20:46
*** tumble has joined #zuul21:20
*** rfolco|rover has quit IRC21:21
*** rfolco|rover has joined #zuul21:26
*** guillaumec has joined #zuul21:27
*** sshnaidm is now known as sshnaidm|afk22:11
*** rfolco|rover has quit IRC22:42
*** kmalloc has joined #zuul22:46
*** tosky has quit IRC22:57
*** sshnaidm|afk has quit IRC23:14
*** sshnaidm has joined #zuul23:15
*** sshnaidm is now known as sshnaidm|afk23:16
*** guillaumec has quit IRC23:16
*** tumble has quit IRC23:47

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!