Christian Aistleitner christian@quelltextlich.at wrote:
--===============2205038051751942713== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline
--Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
Hello everyone,
in the past weeks, I put together "xmldumps-test"---a test suite for Ariel's xmldumps-backup software. xmldumps-test tries to assure that the MySQL database, MediaWiki, and xmldumps-backup play nicely together.
xmldumps-test injects data into the database (so do not use it on a live database), starts xmldumps-backup, and compares the generated XML dumps against pre-verified data. Using xmldumps-test I hope to catch problems caused by modifications to MediaWiki or xmldumps-backup /before/ they hit Wikimedia's production servers dumping enwiki, ...
The code is up for review at https://gerrit.wikimedia.org/r/p/operations/dumps/test.git =2E README serves as general point of entry to the documentation. README.installation shows you how to set up xmldumps-test.
One question:
in the https://gerrit.wikimedia.org/r/p/operations/dumps/test.git repository there are two branches, "master" and "ariel" and the README me says we should use "ariel".
"master" however see to be also attached to a gerrit project
I was able to check it out using
ssh://saper@gerrit.wikimedia.pl/operations/dumps/test.git
port 29418
Which shall we use? It seems that I can propose patches using gerrit only to "master" while "ariel" seems to be a bit more active.
Second thing - I was fixing recently few nuts and bolts for seamless PostgreSQL support, so I'd love to have that for PostgreSQL too. Once I sort out outstanding installer/updater issues I am willing to help, of course.
We already ran a PostgreSQL testsuite on jenkins and I think we should check dumps too.
//Saper