Thursday, 2020-10-29

*** tosky has quit IRC00:06
*** hamalq has quit IRC00:18
*** armstrongs has joined #zuul00:30
mnaserok so i've progressed greatly, while i don't yet wanna mess around with manage-ansible stuff00:34
mnaseri have a pip install module call which succeds but then running my module fails (i moved this thing to an ansible module)00:35
mnaserhttp://paste.openstack.org/show/799495/00:35
mnaserhttp://paste.openstack.org/show/799496/00:36
*** armstrongs has quit IRC00:40
*** mach1na has joined #zuul00:51
*** mach1na has quit IRC00:56
mnaser> Defaulting to user installation because normal site-packages is not writeable00:56
openstackgerritMohammed Naser proposed zuul/zuul master: tools: use python3 for encrypt_secret  https://review.opendev.org/76026601:11
*** jamesmcarthur has joined #zuul01:32
*** jamesmcarthur has quit IRC01:33
*** jamesmcarthur has joined #zuul01:33
*** zenkuro has quit IRC01:39
*** zenkuro has joined #zuul01:40
*** johnsom has quit IRC02:00
*** rpittau|afk has quit IRC02:00
*** ericsysmin has quit IRC02:00
*** maxamillion has quit IRC02:00
*** rpittau|afk has joined #zuul02:00
*** ericsysmin has joined #zuul02:01
*** johnsom has joined #zuul02:01
*** maxamillion has joined #zuul02:02
*** jamesmcarthur has quit IRC02:21
*** zenkuro has quit IRC02:32
*** jamesmcarthur has joined #zuul02:47
*** jamesmcarthur has quit IRC02:56
*** jamesmcarthur has joined #zuul02:56
*** mach1na has joined #zuul02:59
*** mach1na has quit IRC03:03
*** bhavikdbavishi has joined #zuul03:07
*** bhavikdbavishi1 has joined #zuul03:15
*** bhavikdbavishi has quit IRC03:17
*** bhavikdbavishi1 is now known as bhavikdbavishi03:17
*** rlandy|bbl is now known as rlandy03:20
*** jamesmcarthur has quit IRC04:12
*** vishalmanchanda has joined #zuul04:25
*** bhavikdbavishi has quit IRC04:25
*** bhavikdbavishi has joined #zuul04:26
*** mach1na has joined #zuul05:07
*** mach1na has quit IRC05:11
*** evrardjp has quit IRC05:33
*** evrardjp has joined #zuul05:33
*** reiterative has quit IRC05:44
*** reiterative has joined #zuul05:44
*** piotrowskim has joined #zuul05:52
*** mach1na has joined #zuul06:46
*** sshnaidm|afk is now known as sshnaidm|rover07:01
*** EmilienM has quit IRC07:16
*** mach1na has quit IRC07:18
*** mach1na has joined #zuul07:18
*** saneax has joined #zuul07:23
*** bhavikdbavishi has quit IRC07:25
*** jpena|off is now known as jpena07:45
*** pmannidi has quit IRC07:47
*** pmannidi has joined #zuul07:52
*** bhavikdbavishi has joined #zuul07:58
*** jcapitao has joined #zuul08:02
*** yolanda has quit IRC08:24
*** yolanda has joined #zuul08:25
*** sugaar has joined #zuul08:33
*** rpittau|afk is now known as rpittau08:40
*** AJaeger has quit IRC08:42
*** tosky has joined #zuul08:51
*** msuszko has joined #zuul08:54
msuszkoHi, I've noticed Zuul will ignore commits that are just `git merge --no-ff`. Because of this gate won't start, or configuration won't be read from zuul.yaml for soch a change.09:04
msuszkoReason seems to be `no_merges=True` argument here: https://opendev.org/zuul/zuul/src/branch/master/zuul/merger/merger.py#L66809:04
msuszkos/soch/such/09:05
*** vorotech has joined #zuul09:22
*** vorotech has quit IRC09:26
*** zenkuro has joined #zuul09:26
*** zenkuro has quit IRC09:30
*** vorotech has joined #zuul09:32
*** vorotech has quit IRC09:45
*** nilsph has joined #zuul09:47
*** vorotech has joined #zuul09:50
*** bhavikdbavishi has quit IRC10:00
*** hashar has joined #zuul10:07
*** holser has joined #zuul10:07
*** msuszko has quit IRC10:16
*** bhavikdbavishi has joined #zuul10:29
openstackgerritMatthieu Huin proposed zuul/zuul master: zuul-client: test change-status command  https://review.opendev.org/75984010:49
*** wuchunyang has joined #zuul11:14
*** msuszko has joined #zuul11:22
*** jcapitao is now known as jcapitao_lunch11:39
*** zenkuro has joined #zuul11:45
*** msuszko has quit IRC11:45
*** nilsph is now known as nils11:49
*** vorotech has quit IRC11:51
*** wuchunyang has quit IRC12:03
*** rfolco has joined #zuul12:08
*** jpena is now known as jpena|lunch12:19
*** mach1na has quit IRC12:23
*** ianychoi__ is now known as ianychoi12:34
*** zenkuro has quit IRC12:45
*** jcapitao_lunch is now known as jcapitao12:51
sean-k-mooneyso dumb qustionion but any idea why https://github.com/SeanMooney/ci-sean-mooney/blob/main/zuul.d/pipelines.yaml#L2-L39 would reprot only the started message and not success or failure12:56
sean-k-mooneyhttps://review.opendev.org/#/c/750008/ has the "Starting seans-nfv-ci jobs." comments after i trigger it12:58
avasssean-k-mooney: you're trying to set Code-Review.org :)12:58
avassinstead of of Code-Review12:58
sean-k-mooneyoh damit12:58
sean-k-mooneythank you :)12:58
*** mach1na has joined #zuul12:59
*** vorotech has joined #zuul13:01
*** jpena|lunch is now known as jpena13:13
*** bhavikdbavishi has quit IRC13:14
*** bhavikdbavishi has joined #zuul13:14
mnaserso after a long night, i got this working.  it'll check for CODEOWNERS inside the repository, parse that and then add folks in there.  if it sees a /lgtm comment it'll mark as 'reviewed' (but the `vexxhost/lgtm` pipeline still fails), if it gets a `/approve` (similar to work +W), it will update the comment too and the pipeline will pass (which is the trigger to enqueue into gate)13:34
mnaserhttps://usercontent.irccloud-cdn.com/file/UsCjyGDm/image.png13:34
mnaserand it takes around 14 seconds to respond, because it uses a zero node execution action13:34
mnaserso its pretty much mirroring out gerrit system where anyone inside CODEOWNERS can merge13:35
mnaserand allows for self-reviewal too in a super native and easy way13:35
mnaserif there is interest, i can push up the `lgtm` role, and all users need to do is create a pipeline that listens for comments/prs and triggers it13:36
corvusmnaser: that sounds great to me; tobiash ^13:39
mnaserthe only thing that it's kinda lacking is an 'undo' for a lgtm right now, if you delete the comment and write a comment it will trigger it, it looks like we can't trigger on a 'comment deleted' inside github rn13:40
corvusso you can undo by deleting the comment and leaving "/undo" for clarity i guess?13:41
corvusmaybe that's not clear.  maybe leave "removed previous lgtm comment" or something13:41
mnasercorvus: yes, that would be the 'current' workflow right now indeed13:51
mnasergithub usually leaves a 'comment deleted' trace in the messages so that could make sense13:51
tobiashmnaser: so if I understand correctly that's mainly for making self-review possible?13:53
mnasertobiash: correct13:53
tobiashk, I guess that'll be generally usefull13:54
mnasertobiash: and also allowing for both a 'review' and 'approval' (i.e. code-review+2 and workflow+1)13:54
mnaserand also uses CODEOWNERS inside the repo to determine who can review/approve things too13:54
tobiashso if you want to restrict triggering the gate to codeowners as well13:55
mnaseryep, it actually entirely ignores the github acls and relies on codeowners only (so the person that leaves the `/lgtm` doesnt need any right, as long as they are inside CODEOWNERS)13:55
*** bhavikdbavishi has quit IRC14:03
openstackgerritMatthieu Huin proposed zuul/zuul master: Move the testing framework under zuul  https://review.opendev.org/76036114:11
openstackgerritMatthieu Huin proposed zuul/zuul-client master: Move functional tests to zuul-client  https://review.opendev.org/76036314:22
*** zenkuro has joined #zuul14:23
*** vishalmanchanda has quit IRC14:24
openstackgerritMatthieu Huin proposed zuul/zuul-client master: Move functional tests to zuul-client  https://review.opendev.org/76036314:34
*** evrardjp has quit IRC14:38
*** evrardjp has joined #zuul14:40
*** hamalq has joined #zuul14:41
openstackgerritMatthieu Huin proposed zuul/zuul master: Move the testing framework under zuul  https://review.opendev.org/76036114:47
*** zenkuro has quit IRC14:47
*** zenkuro has joined #zuul14:48
openstackgerritMatthieu Huin proposed zuul/zuul master: Move the testing framework under zuul  https://review.opendev.org/76036114:51
tobiashcorvus: we've been hit by an api limitation when reporting line comments to github: https://developer.github.com/v3/checks/runs/#output-object-115:09
tobiashgithub enforces max 50 line comments per PATCH request to the check run15:09
tobiashcorvus: would you prefer to iterate over all line comments or just limit to 50 in zuul and ignore any further line comments?15:10
tobiashiterating would probably make zuul vulnerable for dos attacks as this can block reporting quite a while in extreme cases15:11
clarkbtobiash: if possible it might be good to sort them by uniqueness so that we're reporting the most diverse set of comments possible15:12
tobiashclarkb: how would you judge on that?15:12
clarkbif we have the comment content without filename and line numbers we may be able to put them in a set then pull out 50?15:13
openstackgerritMatthieu Huin proposed zuul/zuul master: Move the testing framework under zuul  https://review.opendev.org/76036115:17
openstackgerritMatthieu Huin proposed zuul/zuul master: Move the testing framework under zuul  https://review.opendev.org/76036115:18
*** jamesmcarthur has joined #zuul15:22
*** jamesmcarthur has quit IRC15:23
*** jamesmcarthur has joined #zuul15:29
*** vorotech has quit IRC15:33
*** jamesmcarthur has quit IRC15:33
mnasertobiash: before i go deep into debuigging, any reason off the top of your mind why this is not queueing into gate?  is it possible that a status _change_ doesn't actually trigger an event? https://www.irccloud.com/pastebin/rpBIk5i1/15:34
tobiashmnaser: that looks ok, but are you using status or check runs for reporting?15:35
tobiasha status change always triggers an event15:35
*** zenkuro has quit IRC15:36
mnasertobiash: i am using check for everything, so maybe that's where i messed up15:36
tobiashmnaser: I mean status api vs check_run api15:36
tobiashoh never mind15:36
mnasermy "lgtm" pipeline https://www.irccloud.com/pastebin/wkbeRE5z/15:36
mhuhey there zuul-maint, here are a few patches that are ready for a final +3: https://review.opendev.org/#/c/728118/ https://review.opendev.org/#/c/751312/ https://review.opendev.org/#/c/754103/ https://review.opendev.org/#/c/755519/15:36
tobiashmnaser: so yes, your pipeline reports a check_run but your trigger wants a status event15:37
tobiashmnaser: just a sec, I'll give you the according check run trigger15:37
mnaserok so i want to listen on `check_run` then15:37
tobiashhttp://paste.openstack.org/show/799515/15:38
*** jamesmcarthur has joined #zuul15:38
tobiashmnaser: note that the requirement stays at status: https://zuul-ci.org/docs/zuul/reference/drivers/github.html#attr-pipeline.require.%3Cgithub%20source%3E.status15:40
tobiashmnaser: that's because github doesn't distinguish that in the branch protection but it does in the events15:40
tobiashso zuul is aligned to that behavior15:40
*** rfolco is now known as rfolco|bbl15:41
tobiashmnaser: however you probably want the gate to listen to status AND check_run success triggers15:41
tobiashmnaser: this way it will interoperate nicely with any other github app regardless if it uses check runs or status api15:41
corvustobiash: i agree that we should limit to 50 and not iterate; i also think it's worth thinking about implementing clarkb's suggestion of aiming for uniqueness; that could help users who have 100 "tabs not spaces" comments and 5 more other useful comments.15:42
tobiash(e.g. all of our projects use the wip bot)15:42
mnasertobiash: so i think this might do it? https://www.irccloud.com/pastebin/M5gShKz7/15:43
tobiashmnaser: you probably want only trigger on success check runs?15:43
mnasertobiash: can i use `status` for `check_run` -- doesn't seem documented?15:44
*** olaph has quit IRC15:44
tobiash?15:44
mnaserif i want to trigger on success check runs only, im not sure i have a way to do that15:45
tobiashjust add: "check: .*:success" to the trigger15:45
mnaserhttps://zuul-ci.org/docs/zuul/reference/drivers/github.html#attr-pipeline.trigger.%3Cgithub%20source%3E.status => "This is used for pull-request and status actions."15:45
mnaserok so i think we may need to document the `check` option on triggers then :D15:45
tobiashmnaser: this will be the your gate pipeline right?15:47
mnasertobiash: correct15:47
mnasertechnically i can even put the trigger only to be ".*/lgtm:success"15:47
mnasercause i don't really ever want to enqueue otherwise15:47
*** holser has quit IRC15:48
tobiashmnaser: well that makes approve impossible before check is done15:48
tobiashmnaser: I'd do this: http://paste.openstack.org/show/799519/15:48
*** holser has joined #zuul15:48
tobiash(ditch the requirement)15:48
tobiashany status/check requirement should be done in the branch protection15:49
tobiashzuul will respect that automatically15:49
mnasertobiash: ok so put the lgtm protection inside github instead15:49
tobiashyes15:49
tobiashthen you can just add any trigger and zuul will do the right thing and enter the gate regardless which event comes first15:50
tobiashthat is a very flexible approach, like we also require WIP from the wip bot in the branch protection15:51
tobiash(and current zuul master now also handles review requirements in github correctly)15:53
*** vorotech has joined #zuul15:59
*** hashar has quit IRC15:59
*** hashar has joined #zuul15:59
*** hashar_ has joined #zuul16:04
*** hashar has quit IRC16:04
mhuHow is Ansible 2.9 installed in Zuul unit tests?16:08
clarkbmhu: I think it uses zuul's ansible install tooling stuff16:10
corvusmhu: ^ yep; the executor installs ansible into the containing venv (ie, the tox pyXX venv)16:11
corvusso it's cached for subsequent tox runs16:11
*** hashar_ is now known as hashar16:24
*** hashar has quit IRC16:25
*** hashar has joined #zuul16:25
*** mach1na has quit IRC16:32
*** jpena is now known as jpena|off16:54
*** mwhahaha has quit IRC16:55
*** mwhahaha has joined #zuul16:55
*** rpittau is now known as rpittau|afk16:57
*** rfolco|bbl is now known as rfolco17:01
*** hamalq has quit IRC17:13
*** hamalq has joined #zuul17:14
mhucorvus: so I should look into zuul's tox.ini?17:18
corvusmhu: no it happens inside of zuul when the first test runs17:18
*** jcapitao has quit IRC17:29
*** zenkuro has joined #zuul17:44
openstackgerritMatthieu Huin proposed zuul/zuul master: Move the testing framework under zuul  https://review.opendev.org/76036117:46
*** vorotech has quit IRC17:46
mnasertobiash: promise that'll be the last question -- you don't by any chance let zuul delete the branch after the merge?17:55
*** hashar has quit IRC18:04
*** vorotech has joined #zuul18:08
*** vorotech has quit IRC18:10
*** tosky has quit IRC18:29
*** piotrowskim has quit IRC18:43
*** jamesmcarthur has quit IRC18:44
tobiashmnaser: there are two possibilities18:59
tobiashfirst, github can delete branches after merge automatically (that's a setting of the repo)18:59
tobiashsecond there is a github app that can automate this as well: https://github.com/apps/baumpfleger19:00
mnasertobiash: oh i didn't know about the auto delete19:02
* mnaser looks for that19:02
mnaser>Automatically delete head branches  indeed19:03
tobiashmnaser: that is a new feature that has been introduced 6 to 12 months ago19:03
tobiashBefore that we used the baumpfleger app19:03
*** zenkuro has quit IRC19:04
*** zenkuro has joined #zuul19:04
*** pabelanger has joined #zuul19:07
pabelangermnaser: I hear you are working on self approvals in github19:07
pabelangerI am very much interested in that19:07
pabelangerthat is basically one of the last things to drop write access to a github repo too19:07
*** zenkuro has quit IRC19:13
openstackgerritMatthieu Huin proposed zuul/zuul master: Move the testing framework under zuul  https://review.opendev.org/76036119:19
*** zenkuro has joined #zuul19:21
*** jamesmcarthur has joined #zuul19:29
*** zenkuro has quit IRC19:31
*** vorotech has joined #zuul20:27
*** jamesmcarthur has quit IRC20:38
*** jamesmcarthur has joined #zuul20:38
openstackgerritAlbin Vass proposed zuul/zuul master: Bump react version  https://review.opendev.org/76045821:00
*** vorotech has quit IRC21:03
*** rfolco has quit IRC21:36
*** sduthil has quit IRC21:46
*** tosky has joined #zuul21:57
*** rlandy has quit IRC22:12
*** jamesmcarthur has quit IRC22:19
*** jamesmcarthur has joined #zuul22:20
*** jamesmcarthur has quit IRC22:25
avasslooks like we can bump react version to 17 without any problems. there are warnings about peer dependencies but since react 17 doesn't add any new features I'm not sure if that's any real problem.22:26
*** jamesmcarthur has joined #zuul22:28
*** vorotech has joined #zuul22:31
*** vorotech has quit IRC22:38
*** vorotech has joined #zuul22:40
*** jamesmcarthur has quit IRC22:41
*** jamesmcarthur has joined #zuul22:42
*** jamesmcarthur has quit IRC22:46
*** vorotech has quit IRC22:49
*** hamalq has quit IRC22:57
*** nils has quit IRC23:01
*** zenkuro has joined #zuul23:14
*** zenkuro has quit IRC23:19
*** zenkuro has joined #zuul23:20

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