Because there have been a number of issues with the run and with branches 1.33-wmf.23 or greater, I'm collecting them all here so I can manage them better.
- T217329 bug in 1.33.0-wmf.18 breaks abstract dumps on testwikidatawiki | MWContentSerializationException $entityId and $targetId can not be the same
- T220160 getRedirectTarget should not automatically load revision content in all cases
- T220316 XmlDumpWriter::openPage handles main namespace articles with prefixes that are namespace names AND are redirects incorrectly
- T220424 XmlDumpWriter::writeRevision sometimes broken by duplicate keys in Link Cache
- T220493 Xml stubs dumps are running 5 to 15x slower than previously
- T220257 dumpBackups.php failing with InvalidArgumentException thrown from RevisionStoreRecord for certain wikis
- T220594 abstracts dumps for dewikiversity fail with MWUnknownContentModelException from ContentHandler.php
- T220793 content still marked as flow-board on urwikibooks breaks abstract dumps
]x T220940 Abstracts dumps for Commons running very slowly
An X next to the task means all the needed dumps patches have been merged and deployed to all wikis. (coming shortly)
These can be summarized as the following:
- stubs run much slower
- abstracts run much slower
- pages with the same key in the link cache now cause fatals during stubs/abstract dumps
- wikibase entities which are self-redirects now cause fatals during abstract dumps
- revisions that are left marked flow-board on wikis which no longer have flow enabled, now cause fatals during stubs/abstract dumps
- attempts to use revisions from a second page for a first page's dump now cause fatals during stubs/abstract dumps
- bad text table entries (typically with DB://cluster20/0) now cause fatals during stubs/abstract dumps
In most cases we need to resolve the issue at two levels: fixing dumps to be more resilient, and fixing the underlying problem (bad revisions, duplicate link cache keys, etc).