Page MenuHomePhabricator

1.36.0-wmf.3 deployment blockers
Closed, ResolvedPublicRelease


Release Version
Release Date
Mon, Aug 3, 12:00 AM
Backup Conductor

2020 week 32 1.36-wmf.3 Changes wmf/1.36.0-wmf.3

This MediaWiki Train Deployment is scheduled for the week of Monday, August 3rd:

Monday August 3rdTuesday, August 4thWednesday, August 5thThursday, August 6thFriday
Backports only.Branch wmf.3 and deploy to Group 0 Wikis.Deploy wmf.3 to Group 1 Wikis.Deploy wmf.3 to all Wikis.No deployments on fridays

How this works

  • Any serious bugs affecting wmf.3 should be added as subtasks beneath this one.
  • Any open subtask(s) block the train from moving forward.This means no further deployments until the blockers are resolved.
  • If something is serious enough to warrant a rollback then you should bring it to the attention of deployers on the #wikimedia-operations IRC channel.
  • For more info about deployment blockers, see Holding the train.

Related Links

Other Deployments

Previous: 1.36.0-wmf.2
Next: 1.36.0-wmf.4

Event Timeline

mmodell created this task.Tue, Jul 14, 8:18 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptTue, Jul 14, 8:19 PM
brennen moved this task from Backlog to Next on the User-brennen board.
brennen added subscribers: brennen, dancy.
Majavah added a subscriber: Majavah.Mon, Aug 3, 7:43 AM

Change 618164 had a related patch set uploaded (by DannyS712; owner: trainbranchbot):
[mediawiki/core@wmf/1.36.0-wmf.3] Branch commit for wmf/1.36.0-wmf.3

brennen moved this task from Next to In Progress on the User-brennen board.Tue, Aug 4, 3:10 PM

Mentioned in SAL (#wikimedia-operations) [2020-08-04T17:03:44Z] <brennen> 1.36.0-wmf.3 was branched at 2d0cf09cdf for T257971

Change 618164 merged by jenkins-bot:
[mediawiki/core@wmf/1.36.0-wmf.3] Branch commit for wmf/1.36.0-wmf.3

Mentioned in SAL (#wikimedia-operations) [2020-08-04T19:03:52Z] <brennen> current 1.36.0-wmf.3 train status (T257971): mid scap-cdb-rebuild for testwiki sync; will proceed with group0 when finished.

Notes at end-of-day:

  • I got a ton of "Ensure local MW versions match expected deployment" alerts while syncing testwikis. Daniel Zahn investigated, seems like a timing issue on the alert.
  • T223287 is still a thing, so that draws out initial sync some.
  • Logs uneventful once deployed to group0. (Logs are noisier than I'd like, but all known issues, nothing specific to .3 yet, as expected for a Tuesday.)

Notes at end-of-day:

  • Log triage meeting today got the new errors dashboard to a pretty clean state, we'll try to keep it that way.
  • Blocked at group0, have hit deploy cutoff, will resume in morning MDT / PDT.

Just filed: T259856

As mentioned there, I'm reluctant to have the train blocked over the weekend for this one, but will be monitoring.

Not a blocker because no new problem, but numbers in T249623#6369185 also look a bit worrisome.

dancy added a comment.Fri, Aug 7, 6:28 PM

Not a blocker because no new problem, but numbers in T249623#6369185 also look a bit worrisome.

Agreed. And it's generating Icinga alerts.

brennen added a comment.EditedFri, Aug 7, 6:31 PM

Not a blocker because no new problem, but numbers in T249623#6369185 also look a bit worrisome.

Yeah, I believe that's actually T226337: SpecialConfirmEmail causes "MWException: CAS update failed on user_touched" from User.php - reopened a bit ago. Like @Aklapper, my current understanding is that it's existing breakage and not specific to wmf.3.

brennen closed this task as Resolved.Fri, Aug 7, 10:15 PM
brennen moved this task from In Progress to Done / Defunct on the User-brennen board.