MediaWiki / MediaWiki 1.30
Event Details
- Week of 12 June
- See https://wikitech.wikimedia.org/wiki/Deployments for full schedule.
Other Deployments:
T166829: MW-1.30.0-wmf.4 deployment blockers T167535: MW-1.30.0-wmf.6 deployment blockers
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | demon | T167533 MW-1.30.0-wmf.5 deployment blockers | |||
| Resolved | Catrope | T167922 [Regression wmf.5] On enhanced watchlists, boldness styling shows regardless of diffs being seen, and a gadget is broken |
Event Timeline
Comment Actions
Looks like T167885: Regression: Backend Save Timing raised by about 50% was caused by wmf.4 - too bad we didn't see this earlier. Dang alerts didn't go off until today.
Comment Actions
from #wikimedia-releng
18:05 <+RainbowSp> Krinkle: Do you think T167885 is a blocker to wmf.5 continuing? 18:05 < stashbot> T167885: Regression: Backend Save Timing raised by about 50% - https://phabricator.wikimedia.org/T167885 18:07 < Krinkle> RainbowSprinkles: Unsure. It should've blocked wmf.4 18:08 < Krinkle> But we found out too late. 18:08 <+RainbowSp> Yeah, that's why I asked. 18:08 < Krinkle> However, there's a fair chance it's related ops ops/db/services instead of mw 18:08 < Krinkle> But too early to tell 18:08 <+RainbowSp> Yeah I read the comments 18:08 <+RainbowSp> Maybe...proceed but we'll watch it closer? 18:09 < Krinkle> RainbowSprinkles: Indeed.
Just noting: I couldn't find a later answer to this question (I presume Performance Team is on it):
18:10 <+RainbowSp> Why did alerts lag? That's concerning