[07:53:27] 10Continuous-Integration-Infrastructure, 10Upstream: Coverage documentation text generated on phpunit/php-code-coverage 9.2.19 is too large - https://phabricator.wikimedia.org/T323654 (10hashar) Nice finding @Reedy :) [09:58:21] (03PS1) 10Vgutierrez: dockerfiles: Use tox-buster on tox-acme-chief [integration/config] - 10https://gerrit.wikimedia.org/r/860839 (https://phabricator.wikimedia.org/T321309) [10:11:48] (03PS2) 10Vgutierrez: dockerfiles: Use tox-buster on tox-acme-chief [integration/config] - 10https://gerrit.wikimedia.org/r/860839 (https://phabricator.wikimedia.org/T321309) [10:13:35] (03PS3) 10Vgutierrez: dockerfiles: Use tox-buster on tox-acme-chief [integration/config] - 10https://gerrit.wikimedia.org/r/860839 (https://phabricator.wikimedia.org/T321309) [10:27:45] (03PS1) 10Vgutierrez: jjb: Use tox-acme-chief:0.6.1 on acme-chief job [integration/config] - 10https://gerrit.wikimedia.org/r/860847 (https://phabricator.wikimedia.org/T321309) [10:37:59] (03CR) 10Hashar: "I am trying a local build since I want to check whether pebble compiles with the go version provided by Buster ;)" [integration/config] - 10https://gerrit.wikimedia.org/r/860839 (https://phabricator.wikimedia.org/T321309) (owner: 10Vgutierrez) [10:38:35] hashar: pebble 1.0 is quite "old", it shouldn't be an issue [10:38:56] thanks for double checking [10:40:11] or maybe the fact it is old prevent it from compiling ;) [10:40:36] hmm ci-buster is been there to build pebble since a long time [10:40:41] it isn't new [10:40:58] we just bumped the base image for the tox tests [10:43:51] oh it is a multiple stages build! [10:44:55] (03PS4) 10Hashar: dockerfiles: Use tox-buster on tox-acme-chief [integration/config] - 10https://gerrit.wikimedia.org/r/860839 (https://phabricator.wikimedia.org/T321309) (owner: 10Vgutierrez) [10:45:07] yep [10:45:34] easy ;) [10:45:39] (03PS2) 10Hashar: jjb: Use tox-acme-chief:0.7.0 on acme-chief job [integration/config] - 10https://gerrit.wikimedia.org/r/860847 (https://phabricator.wikimedia.org/T321309) (owner: 10Vgutierrez) [10:45:41] (03CR) 10Hashar: [C: 03+2] dockerfiles: Use tox-buster on tox-acme-chief [integration/config] - 10https://gerrit.wikimedia.org/r/860839 (https://phabricator.wikimedia.org/T321309) (owner: 10Vgutierrez) [10:48:42] nice :) [10:48:44] (03Merged) 10jenkins-bot: dockerfiles: Use tox-buster on tox-acme-chief [integration/config] - 10https://gerrit.wikimedia.org/r/860839 (https://phabricator.wikimedia.org/T321309) (owner: 10Vgutierrez) [10:48:59] that handles the deploy of the new image or should I trigger it manually? [10:49:58] it is like puppet-merge, we then run docker-pkg manually [10:50:09] via the helper `./fab deploy_docker` [10:50:21] I am hoping to port that to `scap deploy` one day ;-] [10:50:27] ack [10:50:47] which host handles that? [10:56:00] Successfully published image docker-registry.discovery.wmnet/releng/tox-acme-chief:0.7.0 [10:56:16] awesome, thx [10:56:30] vgutierrez: that is one of the contint machine, the primary is reachable via contint.wikimedia.org [10:57:08] vgutierrez: done! [10:57:11] (03CR) 10Hashar: [C: 03+2] "INFO:jenkins_jobs.builder:Number of jobs generated: 1" [integration/config] - 10https://gerrit.wikimedia.org/r/860847 (https://phabricator.wikimedia.org/T321309) (owner: 10Vgutierrez) [11:00:59] (03Merged) 10jenkins-bot: jjb: Use tox-acme-chief:0.7.0 on acme-chief job [integration/config] - 10https://gerrit.wikimedia.org/r/860847 (https://phabricator.wikimedia.org/T321309) (owner: 10Vgutierrez) [11:49:14] 10Release-Engineering-Team (Seen), 10MW-on-K8s, 10SRE, 10Traffic, and 2 others: Serve production traffic via Kubernetes - https://phabricator.wikimedia.org/T290536 (10Joe) [11:49:37] 10Release-Engineering-Team (Seen), 10MW-on-K8s, 10serviceops: Improve performance of deployment to mw on k8s - https://phabricator.wikimedia.org/T323349 (10Joe) 05Open→03Resolved Status update: with the pre-pulling activated, the deployment times for a small patch are in the order of 2-3 minutes on k8s,... [11:52:26] (03PS1) 10Hashar: zuul: add pipelinename to autogenerated:ci tags [integration/config] - 10https://gerrit.wikimedia.org/r/860863 (https://phabricator.wikimedia.org/T214068) [12:05:06] (03PS2) 10Krinkle: zuul: add pipelinename to autogenerated:ci tags [integration/config] - 10https://gerrit.wikimedia.org/r/860863 (https://phabricator.wikimedia.org/T214068) (owner: 10Hashar) [12:05:48] (03CR) 10Krinkle: [C: 03+1] zuul: add pipelinename to autogenerated:ci tags [integration/config] - 10https://gerrit.wikimedia.org/r/860863 (https://phabricator.wikimedia.org/T214068) (owner: 10Hashar) [12:38:13] Krinkle: thanks ;) [12:38:46] (03CR) 10Hashar: [C: 03+2] zuul: add pipelinename to autogenerated:ci tags [integration/config] - 10https://gerrit.wikimedia.org/r/860863 (https://phabricator.wikimedia.org/T214068) (owner: 10Hashar) [12:40:33] (03Merged) 10jenkins-bot: zuul: add pipelinename to autogenerated:ci tags [integration/config] - 10https://gerrit.wikimedia.org/r/860863 (https://phabricator.wikimedia.org/T214068) (owner: 10Hashar) [12:45:29] !log Reloaded Zuul for I717ad1fe4ef7b151808b242cdf16f0268c58fbd7 "add pipelinename to autogenerated:ci tags" # T214068 [12:45:32] Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL [12:45:32] T214068: Display Zuul status of jobs for a change on Gerrit UI - https://phabricator.wikimedia.org/T214068 [13:39:26] (03PS1) 10Hashar: Document how to test a JavaScript Gerrit plugin [software/gerrit] (deploy/wmf/stable-3.5) - 10https://gerrit.wikimedia.org/r/860885 (https://phabricator.wikimedia.org/T214068) [16:26:55] Zuul seems to be stuck? I don’t see any running jobs, only queued ones [16:27:08] cc hashar in case it’s related to the autogenerated:ci things earlier [16:27:25] hmm [16:27:27] damn [16:27:54] Lucas_WMDE: nop unrelated. I have confirmed the autogenerated:ci change does work when reporting to gerrit [16:28:01] ok [16:28:01] I think it is a spike of jobs [16:28:17] there were definitely a lot of jobs earlier today [16:28:19] there is a slight bump in the "Gearman job queue" at the bottom [16:28:34] lots of `assertEmpty()` → `assertSame( [] )` cleanups across extensions [16:29:08] but most of those seem to have merged successfully https://gerrit.wikimedia.org/r/q/topic:AssertEmptyUsed [16:29:40] yeah [16:29:43] this time it is different [16:29:52] it is a bug in zuul that causes it to do too many merge operations [16:29:57] I should get it fixed [16:30:00] maybe [16:30:09] and add a few workers to process those merges [16:30:24] now it’s running again [16:30:27] thanks :) [22:18:19] I wrote way too much javascript tonight https://gerrit.wikimedia.org/r/c/operations/software/gerrit/+/859083/9..10/plugins/wm-checks-api.js :D [22:18:23] merry week-end