Tuesday, 2020-04-28

*** armstrongs has joined #zuul00:01
*** igordc has joined #zuul00:02
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Add ensure-virtualenv  https://review.opendev.org/72330900:10
*** armstrongs has quit IRC00:16
clarkbas a heads up the pinned version of mypy that zuul's tox -e linters runs pulls in an older typed-ast which doesn't work on python3.800:21
clarkbI'm trying to sort that out00:21
clarkbthis is fun. If I change the mypy version I can make tox crash00:26
openstackgerritIan Wienand proposed zuul/nodepool master: Update dib to 2.36.0  https://review.opendev.org/72376100:33
*** igordc has quit IRC00:34
*** rlandy has quit IRC00:42
openstackgerritClark Boylan proposed zuul/zuul master: Bump mypy for py3.8 support  https://review.opendev.org/72376300:45
openstackgerritClark Boylan proposed zuul/zuul master: Don't retry after Gerrit HTTP 409s  https://review.opendev.org/72376400:46
clarkbthat second change is something I noticed onf riday when debugging fun happened00:47
clarkbthe first change was what I noticed when trying to run linters locally under python3.800:47
*** cdearborn has quit IRC01:04
*** rlandy has joined #zuul01:36
*** rlandy has quit IRC01:51
*** swest has quit IRC02:01
*** rf0lc0 has quit IRC02:03
*** rfolco has joined #zuul02:03
*** swest has joined #zuul02:15
*** bhavikdbavishi has joined #zuul03:01
*** bhavikdbavishi1 has joined #zuul03:04
*** bhavikdbavishi has quit IRC03:06
*** bhavikdbavishi1 is now known as bhavikdbavishi03:06
*** threestrands has joined #zuul03:12
openstackgerritIan Wienand proposed zuul/nodepool master: Allow disabling build-log-retention  https://review.opendev.org/72378203:20
openstackgerritMerged zuul/zuul-jobs master: k8-logs: use failed_when: instead of ignore_errors:  https://review.opendev.org/72364703:56
openstackgerritMerged zuul/zuul-jobs master: container-logs: use failed_when: instead of ignore_errors:  https://review.opendev.org/72364803:57
*** sshnaidm|afk is now known as sshnaidm|off04:34
*** evrardjp has quit IRC04:35
*** evrardjp has joined #zuul04:35
*** bhavikdbavishi has quit IRC05:01
clarkbhttps://zuul.opendev.org/t/zuul/build/231db3c20f8d4fa69c3e069e3d6d675c/log/job-output.txt#2114 is a weird failure in zuul's test suite. Seems like the change.message attribute wasn't looking like a string?05:05
clarkbI can'tdebug now but thought I'd call it out05:05
*** bhavikdbavishi has joined #zuul05:17
*** ysandeep|away is now known as ysandeep05:21
*** zenkuro has quit IRC05:35
openstackgerritIan Wienand proposed zuul/nodepool master: Allow disabling build-log-retention  https://review.opendev.org/72378205:47
*** bhavikdbavishi has quit IRC05:54
openstackgerritAndreas Jaeger proposed zuul/zuul master: Revert "Revert "Tune automatic garbage collection of git repos""  https://review.opendev.org/72380005:55
AJaegercorvus, fungi, so this is fine now to revert, correct ^05:57
*** bhavikdbavishi has joined #zuul05:59
*** bhavikdbavishi has quit IRC06:05
*** dpawlik has joined #zuul06:06
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Add ensure-virtualenv  https://review.opendev.org/72330906:09
*** saneax has joined #zuul06:20
*** jcapitao has joined #zuul07:03
*** yolanda has joined #zuul07:18
*** bhavikdbavishi has joined #zuul07:21
*** bhavikdbavishi1 has joined #zuul07:24
*** bhavikdbavishi has quit IRC07:26
*** bhavikdbavishi1 is now known as bhavikdbavishi07:26
*** yolanda has quit IRC07:26
*** yolanda has joined #zuul07:27
*** rpittau|afk is now known as rpittau07:34
*** tosky has joined #zuul07:36
*** bhavikdbavishi has quit IRC07:38
openstackgerritSorin Sbarnea proposed zuul/zuul master: Make task errors expandable  https://review.opendev.org/72353407:40
openstackgerritSorin Sbarnea proposed zuul/zuul master: Make task errors expandable  https://review.opendev.org/72353407:41
*** jpena|off is now known as jpena07:54
*** bhavikdbavishi has joined #zuul08:22
*** ysandeep is now known as ysandeep|lunch08:22
openstackgerritSorin Sbarnea proposed zuul/zuul master: POC: Add convenience Makefile  https://review.opendev.org/72383708:27
zbrdid anyone run zuul unittests under macos? apparently i am not even able to make them start08:36
*** sgw has quit IRC08:41
zbrcreated https://storyboard.openstack.org/#!/story/200760108:42
*** ysandeep|lunch is now known as ysandeep08:53
-openstackstatus- NOTICE: Zuul is currently failing testing, please refrain from recheck and submitting of new changes until this is solved.09:06
*** ChanServ changes topic to "Zuul is currently failing testing, please refrain from recheck and submitting of new changes until this is solved."09:06
-openstackstatus- NOTICE: Zuul is currently failing all testing, please refrain from approving, rechecking or submitting of new changes until this is solved.09:17
*** ChanServ changes topic to "Zuul is currently failing all testing, please refrain from approving, rechecking or submitting of new changes until this is solved."09:17
*** guillaumec has joined #zuul09:48
openstackgerritSorin Sbarnea proposed zuul/zuul master: Fix cherrypy dependency conflict  https://review.opendev.org/72385509:50
openstackgerritSorin Sbarnea proposed zuul/zuul master: Add DOCKER_* to passenv  https://review.opendev.org/72385609:56
*** avass has quit IRC09:59
*** avass has joined #zuul09:59
*** rpittau is now known as rpittau|bbl10:10
*** bhavikdbavishi has quit IRC10:25
*** bhavikdbavishi has joined #zuul10:30
*** Tahvok has quit IRC10:31
*** Tahvok has joined #zuul10:33
*** jcapitao is now known as jcapitao_lunch11:06
*** ysandeep is now known as ysandeep|afk11:07
*** bhavikdbavishi has quit IRC11:09
*** bhavikdbavishi has joined #zuul11:18
*** tosky has quit IRC11:23
*** jpena is now known as jpena|lunch11:35
*** tosky has joined #zuul11:54
mordredzbr: could you fix up 723855 real quick?11:54
zbrhaha, sure11:55
zbrmaybe we need to patch git-review to make it fail on messages not matching 50/72 rule11:56
zbrwhen you get the warning from the server is already too late11:56
mordredzbr: there's actually a gerrit setting to reject things that don't follow the rule - but we never enabled it beause folks thought it was too strict (sometimes a 54 character subject makes more sense)11:57
mordredbut - yeah11:57
avassmordred, zbr: even though I like 'code golfing' with the commit message, 50 characters can be a bit hard to get the meaning across sometimes. especially if you add a topic in the commit message like "build-container-image-docker: now i only have 25 characters left"11:59
avassI'd see it as a guideline12:00
openstackgerritSorin Sbarnea proposed zuul/zuul master: Fix cherrypy dependency conflict  https://review.opendev.org/72385512:00
zbrin fact an interactive prompt would be fine too, the idea is to give user a chance to fix it. printing a warning after you already uploaded it is not.12:01
zbrindeed, there are cases where is ok to ignore the rule12:01
mordredyeah12:06
avasswhat's up with zuul by the way?12:08
AJaegeravass: see backscroll in #opendev12:08
*** rpittau|bbl is now known as rpittau12:08
AJaegeravass: zuul01 run out of memory ;(12:09
avassAJaeger: how do I reach the logs? I usually use the link in the topic :)12:10
mordredyeah - I'm trying to decide whether to restart it to get back up, or wait longer for corvus to look at it12:10
*** guillaumec has quit IRC12:10
AJaegeravass: http://eavesdrop.openstack.org/irclogs/%23opendev/latest.log.html12:12
AJaegeravass: so, not much information to gain12:12
avassshould probably bookmark that12:12
mordredavass: should be back up12:17
*** jcapitao_lunch is now known as jcapitao12:20
*** ChanServ changes topic to "Discussion of the project gating system Zuul | Website: https://zuul-ci.org/ | Docs: https://zuul-ci.org/docs/ | Source: https://git.zuul-ci.org/ | Channel logs: http://eavesdrop.openstack.org/irclogs/%23zuul/ | Weekly updates: https://etherpad.openstack.org/p/zuul-update-email"12:29
-openstackstatus- NOTICE: Zuul has been restarted, all events are lost, recheck or re-approve any changes submitted since 9:50 UTC.12:29
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233912:30
*** rlandy has joined #zuul12:33
*** dpawlik has quit IRC12:36
*** hashar has joined #zuul12:37
*** jpena|lunch is now known as jpena12:38
*** dpawlik has joined #zuul12:40
*** Goneri has joined #zuul12:40
zbrmordred: https://review.opendev.org/#/c/723534/ is also ready for review, loot for a "more" button on that expands the text.12:47
mordredzbr: sadly it totally works - so I cant see the more button ;)12:57
zbrfind a failed build, sadly sharing links does not work with the dashboard12:58
*** bhavikdbavishi has quit IRC12:58
mordredoh - duh12:58
zbrthe button will be present only if output is longer than the limit, but i was lucky, the first failure I checked was longer than the limit12:59
mordredzbr: neat! yes - I found one and it worked as advertised12:59
mordredzbr: we might want to style that more link - my eyes totally missed it even though I was looking for it13:00
zbryep, i was sure someone would say that :D13:00
mordred:)13:01
zbri will have a look, in fact we should be able to even make that pre-wrap setting in the global css13:01
zbri am not yet aware of any case where we do not want the pre-wrap behavior.13:01
avassmordred, zbr: yep, I completely missed that 'more' button13:02
avassI also expected it to be on the bottom so I scrolled past it :)13:02
zbrsure, I will restyle it to make it look like a link. ok about the css question or you prefer in-line?13:02
zbrtbh, i hate in-line, but sometimes is more covenient.13:03
*** sgw has joined #zuul13:07
*** yolanda has quit IRC13:08
*** avass is now known as Guest8097013:10
*** avass has joined #zuul13:10
*** yolanda has joined #zuul13:14
*** rfolco is now known as rfolco|bbl13:34
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: haskell-stack-test: add haskell tool stack test  https://review.opendev.org/72326313:54
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: haskell-stack-test: add haskell tool stack test  https://review.opendev.org/72326314:08
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: tox: Use 'block: ... always: ...' instead of ignore_errors  https://review.opendev.org/72364014:08
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ensure-sphinx: use failed_when: false instead of ignore_errors: true  https://review.opendev.org/72364214:08
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: go: Use 'block: ... always: ...' and failed_when instead of ignore_errors  https://review.opendev.org/72364314:08
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ara-report: use failed_when: false instead of ignore_errors: true  https://review.opendev.org/72364414:08
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: fetch-subunit-output: use failed_when: instead of ignore_errors:  https://review.opendev.org/72365314:08
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: add-build-sshkey: use failed_when: instead of ignore_errors:  https://review.opendev.org/72365414:08
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: tox: Use 'block: ... always: ...' instead of ignore_errors  https://review.opendev.org/72364014:14
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ensure-sphinx: use failed_when: false instead of ignore_errors: true  https://review.opendev.org/72364214:14
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: go: Use 'block: ... always: ...' and failed_when instead of ignore_errors  https://review.opendev.org/72364314:14
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ara-report: use failed_when: false instead of ignore_errors: true  https://review.opendev.org/72364414:14
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: fetch-subunit-output: use failed_when: instead of ignore_errors:  https://review.opendev.org/72365314:14
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: add-build-sshkey: use failed_when: instead of ignore_errors:  https://review.opendev.org/72365414:14
*** ysandeep|afk is now known as ysandeep14:19
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233914:20
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: tox: Use 'block: ... always: ...' instead of ignore_errors  https://review.opendev.org/72364014:20
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ensure-sphinx: use failed_when: false instead of ignore_errors: true  https://review.opendev.org/72364214:20
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: go: Use 'block: ... always: ...' and failed_when instead of ignore_errors  https://review.opendev.org/72364314:20
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ara-report: use failed_when: false instead of ignore_errors: true  https://review.opendev.org/72364414:20
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: fetch-subunit-output: use failed_when: instead of ignore_errors:  https://review.opendev.org/72365314:20
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: add-build-sshkey: use failed_when: instead of ignore_errors:  https://review.opendev.org/72365414:20
avasssorry for that, should be ready now :)14:21
*** fbo is now known as fbo|off14:21
corvusmordred: we restarted on april 20 due to memory pressure, and that was stable for about a week.  i don't think we've merged anything suspicious since then, so we may be looking at a memory leak that was merged before april 20 (possibly a long time ago) but doesn't always manifest.14:23
mordredcorvus: awesome14:26
mordredcorvus: I love issues that only show up sometimes14:27
* AJaeger wonders why zuul01 is already using 10 GB of swap - but has 24 GB of memory free?14:28
*** rpittau is now known as rpittau|brb14:32
mordredcorvus: latest on the multi-arch build - I got through CA certs and /etc/hosts - and it couldn't push to the registry becaues there was no ipv6 address in the builder container ;)14:33
mordredcorvus: latest patch adds net=host - we'll see if that fixes it14:34
corvusAJaeger: that's probably non-zuul related data the kernel previously swapped out; it's not going to load it in until it's used.14:36
*** rfolco|bbl is now known as rfolco14:41
AJaegercorvus: you're probably right - I forgot that we didn't reboot...14:47
corvusavass, AJaeger: i'm looking at approving avass's message to zuul-announce.  do we want to remove the roles in 2 weeks, or do we want to merge a change that reports an error in 2 weeks then remove them 2 weeks after that?14:48
fungiinterestingly, zuul-web is consuming 18.644g vmem with 7g resident according to top14:49
fungiso maybe the memory leak is in there?14:49
corvusclarkb found that we're hitting zuul-web for a lot more than we used to.14:49
fungilooks like the zuul-web container was restarted sometime yesterday14:50
corvusmy guess is perhaps it's using more ram due to the additional load, but it's probably not enough to account for the kind of usage that prompted the scheduler restart14:51
avasscorvus: the second alternative sounds a bit better, forgot that we discussed that yesterday14:52
corvusavass: okay, if you like that approach, how about i discard the message and you can send another one?14:52
corvusavass: (to be clear, the message is still in the moderation queue, so it hasn't been delivered to anyone yet)14:53
avasscorvus: are we looking to implement a warning in the web for the build or so zuul could report 'build: warning' instead of succeeded or error in general?14:54
avasscorvus: yeah go ahead :)14:54
corvusavass: i think a new build state would be a fine idea14:55
*** rpittau|brb is now known as rpittau14:57
avasscorvus: cool14:58
fungiyeah, at the time of the oom, we seem to have had nearly 14g vmem used by the zuul-scheduler process and barely more than 4gb by zuul-web14:58
fungi(at least according to the process report in the kmesg)14:59
*** timburke has quit IRC15:04
avasscrovus: oh, should we go with throwing a warning or fail the jobs to begin with? I'm not sure how long it would take to implementing a new build state15:05
avasscorvus: ^15:05
*** hashar has quit IRC15:15
corvusavass: i think fail the jobs; it'll take a long time for any warning system to actually get deployed by users to be useful15:18
corvusat least if we fail with a message, anyone who ignores the email will quickly know what to fix15:18
avasscorvus: yeah that's what I thought15:18
avasscorvus: I sent a new message15:19
clarkbare the test failures in tests.unit.test_cross_crd.TestGerritToGithubCRD.test_crd_check_unknown a known thing?15:23
clarkbhttps://zuul.opendev.org/t/zuul/build/b702c7815c944819a75300e356c30995/log/job-output.txt#2117 https://zuul.opendev.org/t/zuul/build/231db3c20f8d4fa69c3e069e3d6d675c/log/job-output.txt#2114 I'e caught it failing in two unrelated ways and was checking this isn'y already a known thing before digging further15:24
corvusclarkb: doesn't sound familiar15:31
*** zxiiro has joined #zuul15:33
mordredclarkb: \o/ the multi-arch job passed!15:41
mordredgah15:42
mordredcorvus: ^^ that was menat for you - although hopefully clarkb also finds it exciting15:42
corvusmordred: that's great!  did it run in an ipv6 cloud?  we should make sure that earlier failure case is adequately tested (and it was fixed by the host net, not because it happened to run in ipv4-only)15:44
zbra stupid question: why zuul uses stestr instead of pytest for running tests?15:44
mordredcorvus: that's a great question15:45
clarkbzbr: some of it is history. Zuul existed before pytest. Personally I prefer using a standard complying runner by default which ensures you can use whatever test runner you want. Also testr allows running tests in parallel and is much quicker than pytest15:45
fungizbr: likely because, owing to openstack legacy, we have existing tooling to deal with subunit15:45
mordredyeah. both of those15:45
clarkbyou should be able to run zuul's tests with pytest15:46
clarkbbut if we used pytest by default you'd only be able to use pytest15:46
zbrkindof, you can use pytest w/o using its own features, but like having a ferari with speed-limiter set to 20mph :)15:47
mordredyeah - pytest does the same thing nose did - it's both a test runner and a testing framework - so really there's two sides "why do we use stestr as the runner instead of pytest" and "why do we use testtools as the underlying framework instead of pytest"15:47
fungisome of the testing-cabal folks responsible for testrepository et al were heavily involved in openstack early on15:47
fungiand testtools15:47
zbrpytest used to lack on parallel part, but now both pytest-parallel and pytest-xdist are quite good.15:47
mordredI personally *FAR* prefer testtools to pytest for writing tests - the pytest fixture injection model is too magical to me15:47
mordredso even if I wanted to use pytest as a runner, I'd be very unpleased by using pytest as a test writing base class - at least personally15:48
zbrmordred: indeed, these magic shrooms... are not for everyone.15:48
clarkbmordred: for me its the nose concern15:48
mordredyeah15:48
clarkbmordred: what happens when pytest is abandoned for greener pastures15:48
clarkbnow you're stuck with thousands of lines of useless code15:48
clarkbsticking to stdlib interfaces avoids that15:49
mordredyup!15:49
zbri will have a look to see what is missing for pytest, mainly for dev convenience, like running single test, fail-fast, live progress.15:50
zbrall these features do not require changing the tests15:50
clarkbzbr: correct, but you have no way of enforcing it either15:50
clarkbbecause pytest will happily work with all of its injected non standard stuff15:50
fungialso you can run a single test with testr too15:50
funginot sure what fail-fast and live progress are15:51
clarkbzbr: which is why if we test with testr we can enforce those things without preventing you from using pytest15:51
AJaegermordred: want to abandon https://review.opendev.org/#/c/723109/ with https://review.opendev.org/#/c/723524/6 approved and the stack at https://review.opendev.org/723640 . or do we need 723109?15:51
clarkbpytest should work because we've stuck to standard interfaces15:51
clarkbyou should feel free to use pytest15:51
mordredzbr: stestr tests.test_foo.TestFoo.test_foo runs a single test15:52
mordredsorry15:53
mordredzbr: stestr run tests.test_foo.TestFoo.test_foo runs a single test15:53
zbrbut it lacks a "-x" option, or a way to display the overall progress(baR)15:53
mordredit can print out each test as it runs it15:53
clarkbwhat does -x do?15:53
mordred(which is how I run stestr myself)15:54
zbr-x is --exitfirst15:54
zbrmainly, the fail-fast15:54
mordredotoh - stestr has --failing - which will run only the tests that failed last time15:55
mordredbut seriously - if you like pytest as a test runner - use it15:55
clarkbzbr: --until-failure15:55
mordredclarkb: that's different15:55
clarkbmordred: I think it works the same way though15:55
mordredclarkb: that runs the tests over and over ina. loop until they fail15:55
clarkbmordred: it will exit as soon as it fails15:56
mordredoh - that is a good point15:56
openstackgerritTristan Cacqueray proposed zuul/zuul master: doc: add how to run a single test  https://review.opendev.org/72407215:56
mordredit'll keep running if nothing does fail though15:56
zbraha! i forgot to look for help under "run" command.15:56
clarkbmordred: ya15:56
zbrit has most of the stuff i need, like --pdb :)15:56
mordredzbr: --failing is super cool - it's a great way to iterate on failing tests15:56
clarkbbut ya I think the important point is by enforcing the use of standard interfaces in CI we allow you to use whatever standard compliant test runner you want including pytest15:57
avassmordred: ooh, nice15:57
clarkbif you want to use pytest yu should15:57
zbrout of curiority, when does it save the "failing" status? usually i press Ctrl-C if i see things starting to fail, not wanting to waste too much time.15:57
mordredcorvus, clarkb: any idea why https://review.opendev.org/#/c/722339/ didn't collect /etc/hosts and /home/zuul/.docker/config.json ?15:58
mordredit has host_copy_output in https://review.opendev.org/#/c/722339/17/zuul-tests.d/container-roles-jobs.yaml15:58
clarkbzbr: its streamed to disk as it runs15:58
clarkbzbr: however it is streamed into a temp file until the process ends at which point it is moved into its final location15:59
*** klindgren has quit IRC15:59
clarkbzbr: you can look in .stestrepository and you'll see tmpfiles from when you killed it early15:59
*** klindgren has joined #zuul15:59
zbrokey, i will try to learn more about it, maybe i will write a comparison between the two.16:00
mordredoh - host_copy_output is system-config specific16:03
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233916:03
*** sgw has quit IRC16:04
mordredcorvus: doesn't look like it was an on ipv6 host. any thoughts for how we'd test that?16:04
*** sgw has joined #zuul16:05
clarkbmordred: you want the job to run in openedge or linaro-us for that16:06
clarkband limestone16:06
mordredclarkb: I don't suppose we've got a good way to simulate that in our test job16:07
mordredclarkb: making sure that the role in zuul-jobs works if the host it runs on is ipv6 only relying on zuul-jobs running its test jobs on ipv6 only hosts seems prone to failure16:07
clarkbmordred: ya, but we also have ipv4 only clouds so we can't really do ipv6 only testing reliable?16:08
clarkbthis is one of those things wheer if the world had coalesced on ipv6 in 1998 everything would be great16:08
mordredright?16:10
donnydclarkb: if you use the OE custom labels for the job, wouldn't that ensure it lands on an ipv6 host16:10
donnydor maybe I am missing the point16:11
clarkbdonnyd: it would but I'm not sure we want to force the job to run there as then we'd lose ipv4 testing ?16:11
clarkbsomethign to think about16:11
donnydmaybe two jobs then? one targeted for ipv4 hosts and one for ipv6 ?16:11
clarkbya that might work16:12
corvusmordred: maybe make a throwaway followup change that triggers that job and sets the oe node label, just so we can get a baseline?16:12
donnydisn't vexxhost ipv4? and I think they have the same custom labels as OE16:12
corvusor 2 jobs16:12
openstackgerritJames E. Blair proposed zuul/zuul master: Add serial pipeline manager  https://review.opendev.org/72298116:16
mordreddonnyd: is the label in question nested-virt-ubuntu-bionic ?16:17
corvusmordred, tristanC: ^ serial pipeline updated to use a shared queue16:18
*** rpittau is now known as rpittau|afk16:18
donnydi think you could also use the expanded-* labels16:18
donnydI think this "ubuntu-bionic-expanded"16:19
donnydunless you need nested virt16:19
clarkbexpanded means more memory and is also provided by ipv4 only citycloud16:19
clarkbraelly if we need ipv6 only labels we might want a specific label for that?16:19
donnydand then for ipv4 maybe use ubuntu-bionic-vexxhost16:19
openstackgerritAlbin Vass proposed zuul/zuul master: WIP: Add WARNING build state  https://review.opendev.org/72407816:19
donnydidk if vexxhost is ipv4 only or not though16:20
corvustobiash: re  https://review.opendev.org/722981 (serial pipeline manager) i could rebase that on 718531, or we could do it the other way around.  the serial manager just has a copy of the dependent manager's queue methods, so it should be easy either way.16:20
donnydBetween those two labels is should make your jobs land exclusively on OE and Vexxhost16:20
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233916:21
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: DNM Run builder tests on expanded node  https://review.opendev.org/72407916:21
mordreddonnyd: vexxhost has both - but I think it'll at least increase the chane that with some rechecks we'll hit OE16:21
donnydwell OE has both too - but I think it picks a primary interface16:22
donnydOE has private ipv416:22
openstackgerritMerged zuul/zuul-jobs master: Do not set buildset_fact if it's not present in results.json  https://review.opendev.org/72352416:22
donnydin vexxhost it should pick the ipv4 addr to test against... but then again I know literally nothing about these jobs and how they work16:22
mordredyeha- I think in this case we want the builder node to pick the ipv6 address to talk to the registry node16:23
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: DNM Run builder tests on expanded node  https://review.opendev.org/72407916:23
tobiashcorvus: as you wish. I'm out of office this week so if it blocks you I can rebase mine.16:24
openstackgerritSorin Sbarnea proposed zuul/zuul master: Make task errors expandable  https://review.opendev.org/72353416:28
*** rlandy is now known as rlandy|biab16:34
zbravass: i seen your WARNING feature and reminded me of the UNSTABLE status from jenkins.16:35
*** evrardjp has quit IRC16:35
zbri like the idea, still there is one concern, if I remember well only SUCCESS is a success, anything else is a type of failure.16:35
*** evrardjp has joined #zuul16:35
zbrbut for practical reasons, we may want to define minimum level needed for passing a build, which default should be SUCCESS.16:36
zbrsome jobs may allow the WARNING/UNSTABLE but this should be optional IMHO.16:37
avassfound out that ANSIBLE_EXTRA_PACKAGES doesn't work with the official docker images earlier unless you remove ansible from them first by the way16:37
avasssince ManagedAnsible.validate() only checks if ansible is installed and not if the extra packages is installed16:38
*** TomStappaerts has joined #zuul16:45
*** y2kenny has joined #zuul16:45
TomStappaertsWhen merging several patchsets of the same project but of different branches default behavior is that all of these depend on each other. For my use case they actually do not. Is there a way to make Zuul think that patchsets of the same project are only dependent when they are of the same branch?16:47
tristanCcorvus: thanks, left a couple of comment. Otherwise this is lgtm16:59
tristanC(re the serial pipeline)17:00
clarkbhttps://review.opendev.org/#/c/723763/ is a small change to update mypy in order to support python3.8 if anyone has a moment for that. Thank you tristanC for the quick review17:01
*** jpena is now known as jpena|off17:05
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Support multi-arch image builds with docker buildx  https://review.opendev.org/72233917:06
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: DNM Run builder tests on expanded node  https://review.opendev.org/72407917:06
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Add git name and email for quickstart executor  https://review.opendev.org/72409617:11
*** guillaumec has joined #zuul17:15
*** jcapitao has quit IRC17:39
*** yolanda has quit IRC17:44
*** dpawlik has quit IRC17:48
*** cdearborn has joined #zuul17:51
openstackgerritAlbin Vass proposed zuul/zuul master: Validate ansible extra packages  https://review.opendev.org/72411018:01
*** y2kenny has quit IRC18:03
avass^ that seems to do the trick18:06
openstackgerritAlbin Vass proposed zuul/zuul master: Validate ansible extra packages  https://review.opendev.org/72411018:09
corvusTomStappaerts: we're working on adding that right now actually: https://review.opendev.org/71853118:11
mnaserhey -- is it possible that we merged something that broke jobs with buildset registries?18:17
AJaegermordred: want to abandon https://review.opendev.org/#/c/723109/ with https://review.opendev.org/#/c/723524/6 approved and the stack at https://review.opendev.org/723640 . or do we need 723109?18:18
mnasersee: https://zuul.opendev.org/t/vexxhost/build/2c5e2247629946b18c0d7372def7400618:18
mnaserError initializing source docker://127.0.0.1:51295/vexxhost/openstack-operator:latest: Error reading manifest latest in 127.0.0.1:51295/vexxhost/openstack-operator: error parsing HTTP 404 response body: invalid character18:18
mnaserit looks like the local buildset registry is somehow returning a 404?18:18
*** rlandy|biab is now known as rlandy18:20
mnaserhttps://opendev.org/zuul/zuul-jobs/commit/6fb73060ec919d4e2364e418db84ce6aaa50492d seems to line up with the failures18:20
corvusmnaser: looking18:20
mnaser12:33 pm est i had a change that was ok, this reported at 1:43 pm it was broken, that changed merged in that timeline-ish, i'm reading through it18:22
mnaser(btw my build/upload job also acts as a buildset registry to avoid building 2 vms, cause i always build the docker container anyways)18:22
avassmnaser, corvus: if something is failing there I would guess it's line 13 for some reason18:23
mnaserskipping: Conditional result was False18:24
corvusmnaser: yeah that's it: https://zuul.opendev.org/t/vexxhost/build/2c5e2247629946b18c0d7372def74006/console#3/0/0/ubuntu-bionic18:24
mnaserit skipped "Load information from zuul_return"18:24
corvusit didn't find results.json, but it should have18:24
avasscorvus, mnsaer: aah I see it18:25
mnaserwhat generates results.json ?18:25
mordredthe stat is running on the wrong host18:25
avasscorvus, mnsaer: I missed a delegate_to: localhost on the stat18:25
corvusmnaser: zuul_return module18:25
mordredlookup runs on the executor - the stat is gonna be running on teh remote host18:25
mordredso the stat is goign to fail18:25
mnaserdelegate_to: localhost18:25
avasspushing a fix18:25
mnaseryep that sounds like we all just agreed18:25
mnaseri can depends-on a change too once avass pushes that18:26
TomStappaertscorvus: Thx, will look at upgrading once it is in :D18:26
corvusmnaser: i think you'll have to wait for it to merge; i think that runs in a trusted context18:26
mnaserahhhh yes you're right18:26
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: stat for result.json on the executor  https://review.opendev.org/72411618:26
mordredI agree18:26
mnaser+2 from me avass -- i'll let corvus +w to close it up :)18:27
corvusdone18:27
mnaserok, i'll report back when this lands18:27
mnaserthanks all D:18:28
avasslooks like it fails18:35
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Revert "Do not set buildset_fact if it's not present in results.json"  https://review.opendev.org/72412018:35
mnaseravass: how come its failing?18:35
* mnaser looks18:35
mnaserok yeah18:36
mnaseravass: i guess it's because there's nothing that is doing zuul_return in that test?18:36
mnaserbut results.json seems to exist as an empty file18:37
mnasernot an empty json string18:37
*** ysandeep is now known as ysandeep|away18:37
mordredI'd be willing to bet it's not short-circuit evaluating the when list18:38
avassmordred: I think it is, since we didn't get the exception earlier since it didn't find the file with the stat18:39
mordredah - nod, what mnaser said then18:39
mnaseri could be wrong though18:39
mnaserthe error does seem to imply that the file is emtpy18:39
mnaser"Expecting value: line 1 column 1 (char 0)"18:40
mordredI agree - let's revert - then we can figure it out with less pressure18:40
mordredbecause I really do think this is an improvment18:40
mnaseryes i agree18:40
avassmnsaer, mordred: yeah looks like it throws that exception if it's not a json file18:43
mordredavass: so - maybe we should just check that stat.st_size > 018:45
mordredbecause it should either be empty or have json in it18:45
avassmordred: yeah it's that or somehow check if there's json in it, I'd like the latter18:47
*** saneax has quit IRC18:49
mordredyeah18:50
mordredI would to - if there was a way to do it other than just trying to load it and failing18:50
avassmordred: is the jmespath package installed on the executor?18:52
avassif so the json_query filter works18:52
*** TomStappaerts has left #zuul18:53
avasswait no, nevermind18:53
mordredavass: we need a new module18:54
mordredavass: "load_json_or_none"18:54
mordredthat does a python try: return json.loads(path) except: return None18:54
avassmordred: yeah18:54
mordredavass: almost makes me want to write a custom zuul filter plugin that does that18:58
openstackgerritMerged zuul/zuul-jobs master: Revert "Do not set buildset_fact if it's not present in results.json"  https://review.opendev.org/72412019:09
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Revert "Revert "Do not set buildset_fact if it's not present in results.json""  https://review.opendev.org/72413219:13
avassmordred: I couldn't find a better way so lets just check the filesize19:13
avassmordred: actually, I found a better way19:20
mordredwoot19:20
avassif only slightly19:21
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Revert "Revert "Do not set buildset_fact if it's not present in results.json""  https://review.opendev.org/72413219:23
avassmordred: I guess it's checking for empty string vs checking if filesize > 019:23
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Revert "Revert "Do not set buildset_fact if it's not present in results.json""  https://review.opendev.org/72413219:24
avassmordred: whichever we prefer, compare patchsets 1 vs 3 :)19:24
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Revert "Revert "Do not set buildset_fact if it's not present in results.json""  https://review.opendev.org/72413219:26
avassI take it back, we need that variable undefined. I'm getting too tired to work..19:27
avassI'll check in tomorrow :)19:27
fungii woke up too tired to work. you deserve some rest!19:28
mordredfungi: we're supposed to be working?19:34
*** zxiiro has quit IRC19:36
fungii'm not19:36
fungidepends on how you define "work"19:36
*** threestrands has quit IRC20:09
tristanCzuul-maint : there are a few refactoring change for the zuul-operator to reduce the size of the main resources file. Could you please have a look at the changes between https://review.opendev.org/719965 and https://review.opendev.org/#/c/720024 . Thank you in advance20:10
tristanCit seems like i'm currently the only one pushing for and using the zuul-operator, would it be possible to adopt a lighter approval process?20:25
tristanCi feel bad for requesting reviews repeatedly , but on the other hand jugling with open changes makes it difficult to develop the project20:27
tristanCso would it be possible to implement this workflow: https://github.com/dhall-lang/dhall-lang/blob/master/.github/CONTRIBUTING.md#how-do-changes-get-approved ?20:28
*** dustinc has joined #zuul20:34
clarkbI'll admit to being swamped with a lot of opendev stuff lately20:41
clarkbI personally would be ok with more relaxed operator reviews, but I'm also not a primary consumer/user of it20:41
openstackgerritMerged zuul/zuul master: Bump mypy for py3.8 support  https://review.opendev.org/72376320:44
tristanCin the proposed rules, we could consider the changes that affects the CRD to requires review, then the rest could follow the simplified `rules for merging a change`20:45
openstackgerritMerged zuul/zuul-jobs master: Add ensure-virtualenv  https://review.opendev.org/72330920:51
corvustristanC: tobiash is out this week21:21
corvustristanC: we could adopt a lighter process, but also, he's been a keen reviewer in the past, so i don't know if you want to wait so he doesn't get too far behind :)21:23
corvustristanC: if you want a simplified process, i'd rather not do something complicated and time-based like what's on the dhall page; i'd rather you just ask for reviews of substantial changes and not worry about refactoring changes that don't change the inputs or outputs :)21:26
corvustristanC: i think it's probably fine to merge those 5 changes now21:29
corvustristanC: https://review.opendev.org/716300 apparently depends on https://review.opendev.org/716298 can you look at that?21:31
fungithat's one good thing about a project with comprehensive tests. when a cleanup/refactor doesn't require altering the tests, it's probably safe to approve without rigorous review21:31
clarkbcorvus: what is the expected behavior from Zuul when you depends on a PR or change in an unknown repo?21:38
fungii assumed it was like when you get the url wrong in a depends-on, it just gets ignored21:39
corvusi think what fungi said but not positive21:39
clarkbok, our testing may not quite check that. The reason that our test_crd_check_unknown seems to be failing is that our fake github client doesn't know about the unknown repo and throws and exception21:40
clarkbthis causes gerrit to ignore its known child change too21:41
clarkbwhen the test succeeds it seems to find that repo (which it shouldn't?)21:41
clarkbI'm still trying to unpuzzle what is going on but that helps me set some general expectations21:41
clarkbhttps://opendev.org/zuul/zuul/src/branch/master/tests/unit/test_cross_crd.py#L431-L449 in that test why would we assert B is merged on line 448 is what I think I'm getting at21:43
clarkbsomehow that works most of the time but then like 1/48 test runs locally it fails (and I think the failure is correct)21:43
clarkboh what thats assert false B is merged ok I'm not completely crazy :)21:43
openstackgerritJames E. Blair proposed zuul/zuul master: Add serial pipeline manager  https://review.opendev.org/72298121:46
fungi1:48 is a remarkably precise ratio21:48
clarkbfungi: well I only have one sample as I started looking at logs after my first failure21:52
clarkbI *think* I may know what the issue is21:52
clarkbI've made a change and am running it through the gauntlet21:52
clarkbhowever I don't know that this is asserting correct zuul behavior21:52
openstackgerritMerged zuul/zuul-operator master: Use ensure-* roles  https://review.opendev.org/71940122:00
clarkbthe issue seems related to how we recursively create fake githubclients and githubsessions. https://opendev.org/zuul/zuul/src/branch/master/tests/fakegithub.py#L621 and https://opendev.org/zuul/zuul/src/branch/master/tests/fakegithub.py#L59622:06
clarkbhowever undoing that breaks in new exciting ways22:06
fungithis is the time of day where i tend to not prefer excitation, personally22:09
openstackgerritJames E. Blair proposed zuul/zuul master: Add more docs about pipelines  https://review.opendev.org/72418522:17
openstackgerritAndy Ladjadj proposed zuul/zuul master: Add timezone select on topbar  https://review.opendev.org/72265322:20
openstackgerritAndy Ladjadj proposed zuul/zuul master: Add new timezone selector in web interface  https://review.opendev.org/72265322:21
clarkband I think  Isorted out the race22:25
clarkbnow rerunning through the gauntlet22:25
openstackgerritTristan Cacqueray proposed zuul/zuul-base-jobs master: base: skip role incompatible with kubectl connection  https://review.opendev.org/71629822:29
openstackgerritClark Boylan proposed zuul/zuul master: Fix test_crd_check_unknown tests  https://review.opendev.org/72419122:47
openstackgerritClark Boylan proposed zuul/zuul master: Simplify FakeGithubClient and FakeGithubSession  https://review.opendev.org/72419222:47
clarkbok that stack passed 100 local test runs22:47
clarkbI believe the fix is correct there22:48
openstackgerritJames E. Blair proposed zuul/zuul master: Make fake test Gerrit merger more realistic  https://review.opendev.org/72298223:00
corvusclarkb: thanks, i think one of my changes hit that too23:00
*** Goneri has quit IRC23:39
*** tosky has quit IRC23:39

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