Hello,
Earlier today I slightly changed how Jenkins run the MediaWiki extension job. Specifically the way the database is updated.
We used to simply:
php maintenance/update.php
I wanted to log the SQL queries behind added to the database and the script has a --schema option to do just that. So Jenkins now:
php maintenance/update.php --schema update_sql.log sleep 1 php maintenance/update.php
The sleep is needed because --schema still write to the update_log database. The two runs ends up having the same ul_key in the table since it just vary by timestamp (so if two run occurs in the same second, the second has a duplicate key error).
There should be a better fix, but sleep 1 works ™
Flow had an issue with the tests failing because --schema still run the post-db maintenance script (might be the cause of above problem).
Erik Bernhardson figured out a temporary workaround for Flow:
https://gerrit.wikimedia.org/r/#/c/142303/
The issue is tracked by https://bugzilla.wikimedia.org/67163
Any help welcome!
Le 26/06/2014 21:51, Antoine Musso a écrit :
Erik Bernhardson figured out a temporary workaround for Flow:
https://gerrit.wikimedia.org/r/#/c/142303/
The issue is tracked by https://bugzilla.wikimedia.org/67163
Hello,
I have commented out the update.php --schema call for now. Ie reverted the "feature".
https://gerrit.wikimedia.org/r/142386
wikitech-l@lists.wikimedia.org