Fri, Nov 8
Mon, Nov 4
Thu, Oct 31
Similar cropping up a few times in 1.35.0-wmf.4:
Noting here that this is still cropping up a fair amount as of 1.35.0-wmf.4:
Wed, Oct 30
My sense is that this may or may not block tomorrow's promotion to group2, but probably does not warrant rolling back group1 at present?
This remains pretty noisy in production:
This class of error has led to a lot of noise while tailing logs during this week's train deploy:
Tue, Oct 29
Mon, Oct 28
Fri, Oct 25
I published new docker images, updated job, and re-ran this:
Thu, Oct 24
It's hitting end-of-workday here and I'm a bit fried, will pick up WIP patch in the morning.
Unless I'm mistaken, this should just take adding a package in the list here:
During planning discussions, it came up that we'd like to have this session happen prior to T235372, on the theory that there's a natural progression from one to the other.
Wed, Oct 23
This train is no longer blocked, and can proceed according to schedule. Handing off to @LarsWirzenius.
Only groups 0-1 are affected right now, so enwiki is fine.
Seeing quite a bit of this in production logs at present:
I intended to deploy, but:
Tue, Oct 22
Deployed to group0, updated roadmap. Will reassign task to Lars at EOD.
Fri, Oct 18
Wed, Oct 16
I can co-lead here as well.
Tue, Oct 15
I'd say I usually get a week or so, but it feels like it's happened every other day or so lately. Latest release channel Firefox / Debian, mostly on a single machine.
Oct 13 2019
@Quiddity thoughts here?
Oct 12 2019
@josephine_l I'm primarily attending as a note taker, and should probably focus the time I'm not doing that on local dev and CI sessions. At any rate, I suspect there are considerably better-informed folks than me to lead this one...
Oct 11 2019
One suggestion for a focus: Maintenance & cleanup of existing docs. This has come to mind thinking about docs and new developer onboarding - there's a ton of material but it's not always clear how it relates to the current state of things or how to navigate it. Technical debt lives in the documentation as much as anywhere...
Jeena's comment above covers it (edit: "it" being recent RelEng work) pretty well. We have a local k8s proof-of-concept with Minikube that I think could be used for basic MediaWiki development right now, but the work has led to questions about complexity both for users of the development environment and for maintainers of the environment itself.
It's likely worth mentioning explicitly that we've landed on Argo, after building out and evaluating proofs-of-concept for our final three candidates (Argo, Zuul v3, GitLab CI).
Oct 10 2019
Oct 9 2019
Oct 4 2019
Oct 2 2019
14:05:54 brennen@inertia:~/code/wmf/mediawiki/core (540214-publish-to-dev-1 m0/u0) ☙ docker pull docker-registry.wikimedia.org/wikimedia/mediawiki-core:dev dev: Pulling from wikimedia/mediawiki-core 5c86276767f3: Already exists 0445fd56950a: Pull complete 4edf12b6f5f0: Pull complete 39961bb3a06a: Pull complete ff1bd3a20a43: Pull complete c8d5cc47c664: Pull complete f94c56cc4983: Pull complete 85fda2ab69ff: Pull complete 83f2db0c0f14: Pull complete 3e206fad26b2: Pull complete 739d2f3bb1ec: Pull complete 4c24a7cd82b0: Pull complete 006500bbde5a: Pull complete 332ecb8ca00f: Pull complete 045acbcfc608: Pull complete 061f4db22d8d: Pull complete 7df152ecb998: Pull complete aaee8cf224ae: Pull complete 64dd4ce38455: Pull complete 7ee82f4825b9: Pull complete 3cd5842b704b: Pull complete 27ca13914671: Pull complete 39017c08604a: Pull complete Digest: sha256:5463c6232eee78a6300c40daea12b72e71362d9289e2e05f5d4f1097abec0b01 Status: Downloaded newer image for docker-registry.wikimedia.org/wikimedia/mediawiki-core:dev docker-registry.wikimedia.org/wikimedia/mediawiki-core:dev
Oct 1 2019
Sep 30 2019
Shall we declare this Resolved?