Friday, 2021-03-19

*** vishalmanchanda has quit IRC00:09
*** tosky has quit IRC00:14
*** openstackgerrit has joined #zuul00:46
openstackgerritMerged zuul/zuul master: Report max 50 file comments to github  https://review.opendev.org/c/zuul/zuul/+/76286900:46
*** piotrowskim has quit IRC01:04
*** rlandy has quit IRC01:31
*** hamalq has quit IRC01:39
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: implement support for diskimages  https://review.opendev.org/c/zuul/nodepool/+/78118703:30
*** evrardjp has quit IRC03:33
*** evrardjp has joined #zuul03:33
*** ianychoi has quit IRC03:37
*** vishalmanchanda has joined #zuul04:16
*** ykarel has joined #zuul04:59
*** jfoufas1 has joined #zuul05:28
*** ykarel has quit IRC07:00
*** ykarel has joined #zuul07:02
*** hashar has joined #zuul07:30
openstackgerritSimon Westphahl proposed zuul/zuul master: Improve test output by using named queues  https://review.opendev.org/c/zuul/zuul/+/77562008:21
*** rpittau|afk is now known as rpittau08:24
*** ajitha has joined #zuul08:28
*** tosky has joined #zuul08:54
*** holser has joined #zuul09:00
*** holser has quit IRC09:02
*** holser has joined #zuul09:03
*** ykarel has quit IRC09:11
*** newbie2020 has joined #zuul09:23
newbie2020Hi guys,09:26
newbie2020we have a setup with Zuul 3.18.0 + GitHub.09:26
newbie2020Is it legit to have two PRs on the same repo/project and explicitly adding a 'Depends-On: from one pull request to the other?09:26
newbie2020I do not see why not...09:26
newbie2020But we are getting an "Unknown configuration message" and a colleague is insisting it is not possible to have Depends-On between PRs on the same repo :)09:26
avassnewbie2020: it's working for gerrit so I don't see why you couldn't do that for github unless there's any limitation I'm not aware of09:29
avassI'd expect it to work at least09:30
openstackgerritMatthieu Huin proposed zuul/zuul master: Test zuul-client builds subcommand  https://review.opendev.org/c/zuul/zuul/+/75814109:46
openstackgerritMatthieu Huin proposed zuul/zuul master: test zuul-client build-info  https://review.opendev.org/c/zuul/zuul/+/75878309:47
openstackgerritMatthieu Huin proposed zuul/zuul master: zuul-client: Test buildsets, buildset-info subcommands  https://review.opendev.org/c/zuul/zuul/+/75898509:48
*** ricolin has quit IRC10:01
*** nils has joined #zuul10:13
openstackgerritMatthieu Huin proposed zuul/zuul master: Test zuul-client builds subcommand  https://review.opendev.org/c/zuul/zuul/+/75814110:18
openstackgerritMatthieu Huin proposed zuul/zuul master: test zuul-client build-info  https://review.opendev.org/c/zuul/zuul/+/75878310:24
openstackgerritMatthieu Huin proposed zuul/zuul master: zuul-client: Test buildsets, buildset-info subcommands  https://review.opendev.org/c/zuul/zuul/+/75898510:26
zbravass: any chance to +W https://review.opendev.org/c/zuul/zuul-jobs/+/773245 ? i am worried it will soon need a rebase if we do not.10:34
*** hashar has quit IRC10:37
openstackgerritMatthieu Huin proposed zuul/zuul master: zuul-client: test change-status command  https://review.opendev.org/c/zuul/zuul/+/75984010:37
*** harrymichal has joined #zuul10:40
openstackgerritMatthieu Huin proposed zuul/zuul master: REST API: add api/tenant/{tenant}/jobs/running endpoint  https://review.opendev.org/c/zuul/zuul/+/77164810:41
openstackgerritMatthieu Huin proposed zuul/zuul-client master: Add show running-jobs subcommand  https://review.opendev.org/c/zuul/zuul-client/+/77185310:44
openstackgerritMatthieu Huin proposed zuul/zuul-client master: Add show running-jobs subcommand  https://review.opendev.org/c/zuul/zuul-client/+/77185310:45
*** ykarel|lunch has joined #zuul10:45
openstackgerritMatthieu Huin proposed zuul/zuul master: zuul-client: test "show running-jobs" command  https://review.opendev.org/c/zuul/zuul/+/77196210:45
newbie2020Thanks avass10:48
*** ykarel|lunch is now known as ykarel11:06
avasszbr: done11:16
*** harrymichal has quit IRC11:17
zbrthanks11:22
*** harrymichal has joined #zuul11:35
openstackgerritMerged zuul/zuul-jobs master: Upgrade ansible-lint to 5.0  https://review.opendev.org/c/zuul/zuul-jobs/+/77324511:37
*** rlandy has joined #zuul11:37
*** sassyn has joined #zuul12:00
*** ykarel has quit IRC12:06
*** ykarel has joined #zuul12:07
*** zbr is now known as zbr|rover12:30
*** ykarel has quit IRC12:35
*** ykarel has joined #zuul12:35
openstackgerritBenedikt Löffler proposed zuul/nodepool master: Add zookeeper-timeout connection config  https://review.opendev.org/c/zuul/nodepool/+/75202212:40
*** ajitha has quit IRC13:09
*** jfoufas1 has quit IRC13:33
*** irclogbot_1 has quit IRC13:33
*** openstackgerrit has quit IRC13:33
*** irclogbot_1 has joined #zuul13:37
*** saneax has quit IRC13:40
*** hashar has joined #zuul14:06
corvusnodepool: commit 9fb7c9bb19301b0eacfe30983ce5c0f8436948a2 (HEAD -> master, tag: 4.1.0, origin/master, gerrit/master)14:21
corvuszuul: commit 4bb45bf2a0223c1c624dbd8f44efff207e6b4097 (tag: 4.1.0, refs/changes/69/781169/1)14:21
corvuszuul-maint: ^ i would like to tag and release both of those today14:22
corvus(i think we need both released because there's a matching nodepool/zuul change with shell-type)14:22
corvusthe zuul commit is what i restarted opendev on on wednesday; there are some changes since then, but they aren't critical14:23
corvusopendev has > 24h of zk performance data collected: https://grafana.opendev.org/d/5Imot6EMk/zuul-status?orgId=114:33
corvusso i think we can start merging the initial zk scheduler changes14:34
corvuswe can restart opendev once those land, and if things go poorly, we'll be able to switch back to 4.1.0 easily14:34
mordred++14:40
fungialso opendev is still fairly busy (though not as busy as last week when everyone in openstack was scrambling to make the release feature freeze deadline)14:45
corvusfungi: yeah -- i think it's just the right amount of busy :)  busy enough to have decent data, and not so busy that restarting later would be hugely disruptive.14:47
corvusanyone want to double check those shas? :)14:48
fungilooking14:49
fungifor some reason i have 6de1694f077cf56046997203593ed95313b8380e for zuul's origin/master14:51
avasssame14:52
fungioh, right, stuff has merged since what opendev is running14:52
fungiyeah, three changes in master newer than that point, but since it's what we've seen run in production 4bb45bf2a0223c1c624dbd8f44efff207e6b4097 should be good for 4.1.014:53
*** ykarel has quit IRC14:53
fungiand 9fb7c9bb19301b0eacfe30983ce5c0f8436948a2 looks right for nodepool14:54
fungicorvus: lgtm14:54
corvuscool, i'll push those now14:55
tristanCcorvus: would it be possible to merge the zuul-runner change first?14:58
*** ykarel has joined #zuul15:08
*** rpittau is now known as rpittau|afk15:08
*** chkumar|ruck is now known as raukadah15:24
*** openstackgerrit has joined #zuul15:36
openstackgerritMatthieu Huin proposed zuul/zuul-client master: Add build-info subcommand  https://review.opendev.org/c/zuul/zuul-client/+/75107015:36
fungitristanC: which zuul-runner change, and first before what?15:37
openstackgerritMatthieu Huin proposed zuul/zuul-client master: Add change-status subcommand  https://review.opendev.org/c/zuul/zuul-client/+/75983815:42
*** holser has quit IRC16:05
*** ykarel has quit IRC16:16
*** ykarel has joined #zuul16:17
*** holser has joined #zuul16:18
tristanCfungi: the changes that mostly refactor the executor code, e.g. 607078, 607079, 648642 and 64864316:20
openstackgerritJames E. Blair proposed zuul/zuul master: Resync github permissions docs  https://review.opendev.org/c/zuul/zuul/+/78179316:22
fungitristanC: i think we wanted to run whatever we're going to tag in production on opendev before tagging, so if you're asking to delay 4.1.0 to include those changes, it probably means another zuul restart in opendev. we could always add them in a 4.1.1 or 4.2.0 in a few days though, right? now that we're over the 4.0.0 hump we can go back to releasing as often as is convenient16:28
*** ykarel is now known as ykarel|away16:29
tristanCfungi: oh i meant before other core changes, the 4.1.0 tag looks good to me16:30
fungitristanC: aha, thanks. i was lacking context on "first before what"16:31
*** hashar has quit IRC16:33
avassso how much of the sos stack is planned to be merged now?16:48
corvusi think we're ready for 761163 through 76173816:50
corvusthat moves trigger and management events into zk; we'll be able to observe how that affects performance16:50
corvus(things will probably get a little bit worse before they're able to get better by having more than one scheduler, so a big question is how much worse)16:51
openstackgerritMatthieu Huin proposed zuul/zuul master: REST API, Web UI: add pipelines' manager, triggers data in status  https://review.opendev.org/c/zuul/zuul/+/73696816:55
avassI suppose the java gc could be a performance hit there for big deployments16:58
mordredcorvus: https://review.opendev.org/c/zuul/zuul/+/761164/29 has a failed job17:05
mordredcorvus: it looks unhappy - but I think it was just a test oops and is not related17:07
corvusmordred: yeah, though i don't think it's related to that change17:08
mordredagree17:08
corvuscould be that tests.unit.test_scheduler.TestSchedulerZoneFallback.test_jobs_executed is flakey, caused a timeout, then a cascading failure17:10
corvusi have re-enqueued the zuul release because the docker build failed (npm mirror issues)17:10
clarkbnote if the failure was installing nodeenv it bypasses the npm mirrors iirc17:12
corvus"https://registry.yarnpkg.com/@patternfly/react-tokens/-/react-tokens-4.9.12.tgz: ESOCKETTIMEDOUT".17:13
corvushttps://zuul.opendev.org/t/zuul/build/17448085f19a46208aa650c20410703717:13
corvusso yeah, maybe not the opendev mirrors but the upstream repo17:14
clarkbthat looks to have bypassed the mirror too?17:14
corvusclarkb: probably because it's inside the docker build?17:18
corvusi can't remember where we got to on mirrors-in-docker-builds17:18
clarkbya that could be, but also the js tools have bad habits of ignoring mirror settings ime17:19
clarkbthe nodeenv stuff doesn't even check if they exist iirc17:19
clarkbthey just hardcode urls in their toolign :(17:19
fungiit's the javascript way17:20
fungiprobably they expect you to vendor your own fork of their tools if you need a different url17:21
*** ykarel|away has quit IRC17:31
mordredfungi: or fork their vendored fork17:34
fungioh, yep that17:39
*** newbie2020 has quit IRC17:40
*** hamalq has joined #zuul17:41
openstackgerritMerged zuul/zuul master: Move management and result events to model  https://review.opendev.org/c/zuul/zuul/+/76116318:10
openstackgerritJames E. Blair proposed zuul/nodepool master: Add a state machine driver framework  https://review.opendev.org/c/zuul/nodepool/+/77907118:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Add an example state machine driver  https://review.opendev.org/c/zuul/nodepool/+/77907218:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Improve state machine keyscan handling  https://review.opendev.org/c/zuul/nodepool/+/77937918:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Support threadless deletes  https://review.opendev.org/c/zuul/nodepool/+/77963718:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Add azure state machine driver  https://review.opendev.org/c/zuul/nodepool/+/77942018:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: delete disk based on VM reference  https://review.opendev.org/c/zuul/nodepool/+/77989718:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: reconcile config objects  https://review.opendev.org/c/zuul/nodepool/+/77989818:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: Handle IPv6  https://review.opendev.org/c/zuul/nodepool/+/78040018:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: don't require full subnet id  https://review.opendev.org/c/zuul/nodepool/+/78040218:12
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: add quota support  https://review.opendev.org/c/zuul/nodepool/+/78043918:13
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: implement launch retries  https://review.opendev.org/c/zuul/nodepool/+/78068218:13
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: implement support for diskimages  https://review.opendev.org/c/zuul/nodepool/+/78118718:13
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: handle leaked image upload resources  https://review.opendev.org/c/zuul/nodepool/+/78185518:13
openstackgerritJames E. Blair proposed zuul/nodepool master: Azure: use rate limiting  https://review.opendev.org/c/zuul/nodepool/+/78185618:13
corvusanother zuul release failure: 1mE: Failed to fetch https://deb.nodesource.com/node_10.x/pool/main/n/nodejs/nodejs_10.24.0-1nodesource1_amd64.deb  Could not connect to deb.nodesource.com:443 (104.123.50.113), connection timed out Could not connect to deb.nodesource.com:443 (104.123.50.89), connection timed out18:13
corvusre-enqueing18:13
mordredcorvus: jeez18:16
mordredcorvus: that's the nodeenv stuff clarkb was mentioning before probably right?18:19
openstackgerritMerged zuul/zuul master: Allow (de-)serialization of management events  https://review.opendev.org/c/zuul/zuul/+/76116418:21
openstackgerritMerged zuul/zuul master: Add and fix fields in driver trigger event models  https://review.opendev.org/c/zuul/zuul/+/76116618:22
openstackgerritMerged zuul/zuul master: Allow (de-)serialization of trigger events  https://review.opendev.org/c/zuul/zuul/+/76116718:23
mordredcorvus: did you re-enqueue it before it reported? I was looking for the failure in zuul and don't see it18:24
openstackgerritMerged zuul/zuul master: Interface to get a driver's trigger event class  https://review.opendev.org/c/zuul/zuul/+/76116818:24
corvusmordred: this one https://zuul.opendev.org/t/zuul/buildset/637952fb323b4350bef44f1b30aaa29a18:25
mordredcorvus: ahhh - thanks18:26
clarkbmordred: ya I think that is how it manifests18:26
mordredwell - fwiw, this isn't even nodeenv or other javascript hardcoding - this is us hardcoding the nodesource deb repo in install-js-tools18:27
mordredI don't know that we'd get it right in the Dockerfile if we improved install-js-tools - that would be a whole other layer of work18:27
mordredthat said ... https://review.opendev.org/c/zuul/zuul/+/728690 would potentially make this part a bit more resilient18:30
clarkbhttps://github.com/ekalinin/nodeenv/blob/master/nodeenv.py#L1042-L1053 looks like nodeenv did add a flag for setting a mirror18:32
openstackgerritMatthieu Huin proposed zuul/zuul master: web UI: allow a privileged user to promote a change  https://review.opendev.org/c/zuul/zuul/+/78185818:32
mordredclarkb: yah - but in this case we're not using nodeenv18:33
openstackgerritMatthieu Huin proposed zuul/zuul master: Example Docker compose: keycloak integration  https://review.opendev.org/c/zuul/zuul/+/76994318:34
openstackgerritMonty Taylor proposed zuul/zuul master: Use node image to build javascript  https://review.opendev.org/c/zuul/zuul/+/72869018:34
openstackgerritMonty Taylor proposed zuul/zuul master: Use node image to build javascript  https://review.opendev.org/c/zuul/zuul/+/72869018:35
*** hamalq has quit IRC18:36
openstackgerritMatthieu Huin proposed zuul/zuul master: Example Docker compose: keycloak integration  https://review.opendev.org/c/zuul/zuul/+/76994318:36
*** hamalq has joined #zuul18:36
mordredclarkb: I thnik three different mirrors we'd need in the general case - one for npm - but also one for the node deb repo and one for the yarn deb repo18:37
openstackgerritMatthieu Huin proposed zuul/zuul master: Example Docker compose: keycloak integration  https://review.opendev.org/c/zuul/zuul/+/76994318:39
mhuso I've got a baby pretty much about to pop in the gate pipeline, most likely next week ... the admin web ui patch chain at https://review.opendev.org/q/topic:%22fffaff%22 should be in a reviewable state; the docker compose has everything except for the autohold(s) page18:43
mordredmhu: so when you say baby here, you mean a small human not a patch series you've been working on18:44
mhuif someone wants to take over while I am knee deep in diapers feel free to18:44
mhumordred, is there a difference?18:44
mordredhahaha. I believe one produces more poop - otherwise, no?18:44
mordredcongratulations in advance!18:44
mhubut yeah, my gf has been working hard on releasing mhu 2.018:44
mordredI'm sure she'll appreciate being called a gate pipeline ;)18:45
mhushe moderately appreciated the zuul sticker on her belly!18:46
mordredmhu: how long before 2.0 starts submitting patches - we can use more hands around here18:46
mordredhahahaha! nice18:46
mhumordred: pretty much on day 1, if you're not picky about code quality18:47
corvusmordred: wait, which one makes poop again? :)18:47
mordredcorvus: yes18:47
corvusmhu: that's great news!  :)18:47
clarkbthe day they take care of poop themselves is a glorious day18:48
mhucorvus, thanks! with less sleeping time, I can code more!18:48
corvusthat's really the whole idea of test-driven development, right?  "clean up your own poop"18:49
clarkbcorvus: yes, but it comes with emergent behaviors18:51
*** rlandy is now known as rlandy|training18:57
*** harrymichal has quit IRC19:02
*** harrymichal has joined #zuul19:22
*** vishalmanchanda has quit IRC19:35
corvusokay, the docker 410 job finally succeeded, so both codebases are now released.  i'll send out notices shortly.19:59
*** rlandy|training is now known as rlandy20:04
openstackgerritMerged zuul/zuul master: Implementation of Zookeeper backed event queues  https://review.opendev.org/c/zuul/zuul/+/76117020:59
*** rlandy has quit IRC21:15
*** openstackgerrit has quit IRC21:22
*** harrymichal has quit IRC21:59
*** dpawlik has quit IRC22:11
*** dpawlik9 has joined #zuul22:12
*** dpawlik9 is now known as dpawlik22:13
*** kgz has quit IRC22:13
*** tobiash has quit IRC22:13
*** tobiash has joined #zuul22:14
*** mgoddard has quit IRC22:16
*** jpena|off has quit IRC22:16
*** kgz has joined #zuul22:17
*** jpena|off has joined #zuul22:18
*** mgoddard has joined #zuul22:19
*** nils has quit IRC22:39
*** sshnaidm|off has quit IRC22:54
*** hamalq has quit IRC23:05
*** holser has quit IRC23:49

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