Re: [Wikitech-l] Test Mailman3 in production

[Deb Tankersley]

Hi,

I've started to play with the interface, but questioning a bit the
instructions given (for clarity purposes) when you're signing up for a list:

Before you can start using GNU Mailman at this site, you must first confirm
> that this is your email address.  You can do this by replying to this
> message,
> keeping the Subject header intact.
>

Should there be additional instructions on if something is needed in the
body of that reply email, or that it can be empty and just keep the subject
line the same?

Cheers,

Deb

--

deb tankersley (she/her)

senior program manager, engineering

Wikimedia Foundation



On Fri, Mar 26, 2021 at 3:40 AM Pankaj Jangid 
wrote:

> Amir Sarabadani  writes:
>
> > tl;dr: https://lists-next.wikimedia.org is running mailman3. Please
> help us
> > test the software before we upgrade the real mailing list server.
>
> Indeed this is great news. I have subscribed to a couple of mailing
> lists that are already using v3. And it really makes it easy to
> manage. Thanks for working on this.
>
> One question. I subscribe to this list via the NNTP bridge hosted at
> gmane.io. Will the change make any difference at that end? I mean do the
> administrators of Gmane require any change?
>
> --
> Regards,
> Pankaj Jangid
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test Mailman3 in production

[Pankaj Jangid]

Amir Sarabadani  writes:

> tl;dr: https://lists-next.wikimedia.org is running mailman3. Please help us
> test the software before we upgrade the real mailing list server.

Indeed this is great news. I have subscribed to a couple of mailing
lists that are already using v3. And it really makes it easy to
manage. Thanks for working on this.

One question. I subscribe to this list via the NNTP bridge hosted at
gmane.io. Will the change make any difference at that end? I mean do the
administrators of Gmane require any change?

-- 
Regards,
Pankaj Jangid


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test Mailman3 in production

[Amir Sarabadani]

Hello,

tl;dr: https://lists-next.wikimedia.org is running mailman3. Please help us
test the software before we upgrade the real mailing list server.

Kunal and I have been working on deploying the new mailman (version 3) to
replace mailman2 serving https://lists.wikimedia.org and powering all of
our mailing lists.

Mailman2 is a dinosaur that should have gone extinct years ago. Pretty old
user interface (especially for admins and moderators), storing passwords in
plain text, lack of any database (everything is file on disk), pretty old
code, lack of ability to search in archives or send email from web
interface, running on EOL python (python2), encoding issues with non-Latin
languages, hard to redact archives, and the list goes on and on.

The new version has been developed/puppetized/tested in the Cloud and is
now ready for proper testing! Give it a try:
https://lists-next.wikimedia.org. We have created some mailing lists you
can join and can test. If you want to test the experience as a list
administrator/moderator, we can give those permissions out as well.

WARNING: All data on the lists-next server will be deleted after the test
period is over.

We will also need help updating documentation on wikis and elsewhere.

If you find any bugs/issues (yay!), please file a ticket in the
“Wikimedia-Mailing-lists” Phabricator project and we’ll check it out.

In the coming days/weeks will also import some public mailing lists from
the old version to the new version to check archive size, search index
size, and other aspects. There are other TODOs left as well like
monitoring, logging, anti-abuse, etc.

Slowly and after testing (hopefully soon), we expect to deploy this on
lists.wikimedia.org and mailing lists one by one or in batches can be
upgraded to the 21st century.

The overall task tracking this project is T52864
 and a big thank you people who
are helping this move forward.

Regards,

Kunal and Amir
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test runner Quibble 0.0.46 released

[Kosta Harlan]

Thanks Timo :) However just to clarify, the vast majority of credit for that 
feature goes to Adam Wight, both for the final set of patches and a series of 
refactoring patches earlier this year that made the httpd integration possible. 
Thank you Adam!

Kosta

> On 14. Jan 2021, at 02:33, Krinkle  wrote:
> 
> 
> 
> Thanks Kosta and Antoine. Very exciting.
> 
> Follow the roll out of Apache vs PHP dev server, at:
> https://phabricator.wikimedia.org/T225218 
> 
> 
> -- Timo
> 
> 
> On Thu, Jan 7, 2021 at 7:55 PM Antoine Musso  > wrote:
> Hello,
> 
> I am pleased to announce the release of Quibble 0.0.46 mainly driven by 
> Adam Wight && Kosta Harlan.
> 
> 
> The major feature is support for using an external web server such as 
> Apache. The php builtin server driven by Quibble serves requests 
> serially and does not offer all the customization Apache can do.
> 
> The source repository has an example Dockerfile that leverage the use of 
> supervisord to spawn Apache and point Quibble to it. We will roll that 
> system to the CI jobs progressively over the next few weeks.
> 
> The journey started when Kosta benchmarked php vs Apache and by serving 
> requests in parallel we have already addressed issues found in MediaWiki 
> test suites.
> 
> Python 3.8 is officially supported, 3.4 or earlier are no more tested 
> and if still using those you should really upgrade.
> 
> Running under podman (a daemonless alternative to docker) is now 
> recognized as a container environment (thanks Marius Hoch).
> 
> 
> Doc: https://doc.wikimedia.org/quibble/ 
> Changelog: https://doc.wikimedia.org/quibble/changelog.html 
> 
> Source: https://gerrit.wikimedia.org/g/integration/quibble/
> Bug/features 
> : #quibble 
> tag in Phabricator
> 
> Quibble introduction: https://phabricator.wikimedia.org/J99 
> 
> 
> cheers,
> 
> -- 
> Antoine "hashar" Musso
> 
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org 
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l 
> 
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test runner Quibble 0.0.46 released

[Krinkle]



Thanks Kosta and Antoine. Very exciting.

Follow the roll out of Apache vs PHP dev server, at:
https://phabricator.wikimedia.org/T225218

-- Timo


On Thu, Jan 7, 2021 at 7:55 PM Antoine Musso  wrote:

> Hello,
>
> I am pleased to announce the release of Quibble 0.0.46 mainly driven by
> Adam Wight && Kosta Harlan.
>
>
> The major feature is support for using an external web server such as
> Apache. The php builtin server driven by Quibble serves requests
> serially and does not offer all the customization Apache can do.
>
> The source repository has an example Dockerfile that leverage the use of
> supervisord to spawn Apache and point Quibble to it. We will roll that
> system to the CI jobs progressively over the next few weeks.
>
> The journey started when Kosta benchmarked php vs Apache and by serving
> requests in parallel we have already addressed issues found in MediaWiki
> test suites.
>
> Python 3.8 is officially supported, 3.4 or earlier are no more tested
> and if still using those you should really upgrade.
>
> Running under podman (a daemonless alternative to docker) is now
> recognized as a container environment (thanks Marius Hoch).
>
>
> Doc: https://doc.wikimedia.org/quibble/
> Changelog: https://doc.wikimedia.org/quibble/changelog.html
> Source: https://gerrit.wikimedia.org/g/integration/quibble/
> Bug/features
> :
> #quibble tag in Phabricator
>
> Quibble introduction: https://phabricator.wikimedia.org/J99
>
> cheers,
>
> --
> Antoine "hashar" Musso
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test runner Quibble 0.0.46 released

[Antoine Musso]

Hello,

I am pleased to announce the release of Quibble 0.0.46 mainly driven by 
Adam Wight && Kosta Harlan.



The major feature is support for using an external web server such as 
Apache. The php builtin server driven by Quibble serves requests 
serially and does not offer all the customization Apache can do.


The source repository has an example Dockerfile that leverage the use of 
supervisord to spawn Apache and point Quibble to it. We will roll that 
system to the CI jobs progressively over the next few weeks.


The journey started when Kosta benchmarked php vs Apache and by serving 
requests in parallel we have already addressed issues found in MediaWiki 
test suites.


Python 3.8 is officially supported, 3.4 or earlier are no more tested 
and if still using those you should really upgrade.


Running under podman (a daemonless alternative to docker) is now 
recognized as a container environment (thanks Marius Hoch).



Doc: https://doc.wikimedia.org/quibble/
Changelog: https://doc.wikimedia.org/quibble/changelog.html
Source: https://gerrit.wikimedia.org/g/integration/quibble/
Bug/features: #quibble tag in Phabricator

Quibble introduction: https://phabricator.wikimedia.org/J99

cheers,

--
Antoine "hashar" Musso

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test Install of MediaWIki for Experimentation

[bawolff]

There is also https://en.wikipedia.beta.wmflabs.org/wiki/Main_Page &
https://commons.wikimedia.beta.wmflabs.org/wiki/Main_Page
test.wikipedia.org is closer to the main site (running basically the
version of MW used on wikipedia, and all the user accounts are integrated),
and should not be used for any sort of testing that could be "disruptive".
the test wikis under *.beta.wmflabs.org are more experimental, and runs the
most latest version of mediawiki. Generally I'd recommend testing on the
beta site since it is using the absolute newest version of MediaWiki.

--
Brian

On Thu, Nov 21, 2019 at 9:14 PM Zoran Dori  wrote:

> Hi,
> there is https://test.wikipedia.org https://test2.wikipedia.org
>
> If you want to install it on your own, see
> https://www.mediawiki.org/wiki/Manual:Installation_guide
>
> Best regards,
> Zoran.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test Install of MediaWIki for Experimentation

[Egbe Eugene]

Thanks very much Zoran.

On Thu, 21 Nov 2019 at 22:14 Zoran Dori  wrote:

> Hi,
> there is https://test.wikipedia.org https://test2.wikipedia.org
>
> If you want to install it on your own, see
> https://www.mediawiki.org/wiki/Manual:Installation_guide
>
> Best regards,
> Zoran.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test Install of MediaWIki for Experimentation

[Zoran Dori]

Hi,
there is https://test.wikipedia.org https://test2.wikipedia.org

If you want to install it on your own, see
https://www.mediawiki.org/wiki/Manual:Installation_guide

Best regards,
Zoran.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test Install of MediaWIki for Experimentation

[Egbe Eugene]

Hi All,

is there a test version of MediaWiki which is open to developers such as
test commons and the rest?

Thanks
Eugene
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] TEST

[80hnhtv4agou--- via Wikitech-l]

 TEST
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] test

[John D.]

test
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test coverage reports for patchsets

[Kunal Mehta]

Hi,

I've been working on a tool, phpunit-patch-coverage[0], that tries to
provide test coverage reports for patches before they are merged[1].
Since it takes 2-3 hours to do a full coverage report for MediaWiki
core, the tool figures out what files were modified, and runs those tests.

For now I've set up a job that runs for MediaWiki core, and leaves a
comment like "PHP test coverage increased (or stayed the same)"[2] or
"PHP test coverage decreased :-("[3]. This job is slow so it is run
separately from unit tests to avoid delaying that feedback.

I'm sure there are bugs, please report them in the Phabricator
project[4], along with any feature requests on how we can make this
more useful. This should be considered beta quality software for now :-).

[0] https://packagist.org/packages/mediawiki/phpunit-patch-coverage
[1] https://phabricator.wikimedia.org/T101544
[2] https://gerrit.wikimedia.org/r/#/c/407592/
[3] https://gerrit.wikimedia.org/r/#/c/407157/2
[4] https://phabricator.wikimedia.org/project/profile/3222/

-- Legoktm



signature.asc
Description: OpenPGP digital signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] test: Jenkins crashed again today

[Antoine Musso]

Le 10/05/13 00:00, Antoine Musso a écrit :
 Hello,
 
 Jenkins crashed again today. The first time at 6am UTC, I got it fixed.
 And again between 9pm and 10pm UTC.
 
 This has been a recurring event since we have upgraded our installation
 and the bug is:
  https://bugzilla.wikimedia.org/show_bug.cgi?id=48025
 
 Tonight I got Jenkins access log enabled and made Zuul query jenkins
 directly instead of passing via SSL + an Apache frontend proxy.  That
 will help a little bit.
 
 The root cause is some weird issue in Jenkins where one of its thread
 will use 100% CPU.  I have yet to determine what that thread is doing
 though nor what trigger the exact issue.  Whenever I get some useful
 informations I will fill a bug upstream and make sure it get attention.

So I went to bed, and in the morning Jenkins was unsurprisingly stuck
again.  Enjoying coffee and croissant, my morning newspapers have been
replaced by obscure web browsers windows titled:
  how to read a java heap dump
  help reading a 2GB head dump (trivia: you need a ton of memory)
  java stack trace
  google: enable java debugging symbols
  Garbage Collection in the Java HotSpot Virtual Machine [1]

All of that while breaking the #1 WMF rule: do not work in pyjama.

I found out the Java Heap memory was full.

Also took time to look at a Jenkins notice that is warning about some
mysterious old data format.  After some reading, they are XML elements
from the history build files which points to non existent entry points
in Jenkins.  That can happens when a plugin is removed.

When Jenkins parse the build history, it will record an in memory entry
for each occurrences, with the thousands of builds we keep, that turns
in a memory killer.

Jenkins offer the possibility to clean the, now invalid, elements for us
but it is eventually terribly slow.  I thus resurrected my sed skills
and altered the XML file.  That ran from 12:25am UTC till 17:19am UTC.

The invalid data gone, I hope Jenkins is not going to fill its memory
again :-] I will monitor that tonight and on Monday then probably call
it done.


I am really sorry for the multiple inconveniences since the upgrade on
May 2nd and for the long time it took me to figure out the issue :(


Thanks Chad for the helpful tips regarding Java Heap memory size and
thank you Timo for the Java Melody monitoring system.




The bug report:
  https://bugzilla.wikimedia.org/show_bug.cgi?id=48025#c19


[1] http://www.devx.com/Java/Article/21977   recommended reading


-- 
Antoine hashar Musso


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] test: Jenkins crashed again today

[Antoine Musso]

Hello,

Jenkins crashed again today. The first time at 6am UTC, I got it fixed.
And again between 9pm and 10pm UTC.

This has been a recurring event since we have upgraded our installation
and the bug is:
 https://bugzilla.wikimedia.org/show_bug.cgi?id=48025

Tonight I got Jenkins access log enabled and made Zuul query jenkins
directly instead of passing via SSL + an Apache frontend proxy.  That
will help a little bit.

The root cause is some weird issue in Jenkins where one of its thread
will use 100% CPU.  I have yet to determine what that thread is doing
though nor what trigger the exact issue.  Whenever I get some useful
informations I will fill a bug upstream and make sure it get attention.

Next secret plan: get rid of Jenkins..

-- 
Antoine hashar Musso


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] test gossip

[Sumana Harihareswara]

A few things I learned recently by gossiping with WMF quality assurance
people:

We're deploying fresh code to the beta cluster ~50 times a day, or maybe
even more often!
https://gerrit.wikimedia.org/r/#/q/status:merged+project:%255Emediawiki.*+-owner:l10n-bot,n,z
shows merged code to MediaWiki core  extensions -- on every merge or
every few minutes, we update the code on
http://commons.wikimedia.beta.wmflabs.org/ and all the other beta
cluster sites.  So right now, beta is the best target for automated
browser tests, but because of some configuration issues,
http://test2.wikipedia.org/ is the best target for manual/exploratory
testing.

When you're writing automated browser tests (good setup instructions:
https://github.com/wikimedia/qa-browsertests ), feature files are a
plain-English communication tool; step definitions are where the magic
happens.  So, in features/ , there's step_definitions/ with .rb files,
each corresponding to a feature file.  Look through those for some idea
of the neat stuff we can do these days.

If you want ideas for useful automated browser tests to write, try
looking at recently fixed bugs.  That way we'll catch regressions.

-- 
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] test gossip

[Siebrand Mazeland (WMF)]

Very helpful, Sumana. I'd happily encourage more gossip of this type.


On Thu, Apr 11, 2013 at 12:40 AM, Sumana Harihareswara 
suma...@wikimedia.org wrote:

 A few things I learned recently by gossiping with WMF quality assurance
 people:

 We're deploying fresh code to the beta cluster ~50 times a day, or maybe
 even more often!

 https://gerrit.wikimedia.org/r/#/q/status:merged+project:%255Emediawiki.*+-owner:l10n-bot,n,z
 shows merged code to MediaWiki core  extensions -- on every merge or
 every few minutes, we update the code on
 http://commons.wikimedia.beta.wmflabs.org/ and all the other beta
 cluster sites.  So right now, beta is the best target for automated
 browser tests, but because of some configuration issues,
 http://test2.wikipedia.org/ is the best target for manual/exploratory
 testing.

 When you're writing automated browser tests (good setup instructions:
 https://github.com/wikimedia/qa-browsertests ), feature files are a
 plain-English communication tool; step definitions are where the magic
 happens.  So, in features/ , there's step_definitions/ with .rb files,
 each corresponding to a feature file.  Look through those for some idea
 of the neat stuff we can do these days.

 If you want ideas for useful automated browser tests to write, try
 looking at recently fixed bugs.  That way we'll catch regressions.

 --
 Sumana Harihareswara
 Engineering Community Manager
 Wikimedia Foundation

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Siebrand Mazeland
Product Manager Language Engineering
Wikimedia Foundation

M: +31 6 50 69 1239
Skype: siebrand

Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] [test] style check on mediawiki/core

[Antoine Musso]

Hello,

I have finally integrated PHP_CodeSniffer to report PHP style errors in
MediaWiki core.  PHP_CodeSniffer tokenises PHP and detects violations
based on a set of coding standards.


You can get it running on your local installation by following the very
lame install guide I wrote at mw.org :

https://www.mediawiki.org/wiki/Continuous_integration/PHP_CodeSniffer#installing


Whenever a new patchset is uploaded in Gerrit, Jenkins will run phpcs on
each file modified by the patchset and report the errors. The status
points to the console for example:

 https://integration.mediawiki.org/ci/job/mediawiki-core-phpcs-HEAD/30/console

From there click on the left on the Violations link to get a meaningful
report and a details of violations per file.  Ex:

https://integration.mediawiki.org/ci/job/mediawiki-core-phpcs-HEAD/30/violations/file/maintenance/eval.php/?


Don't worry, it is not going to block merge since the result status is
actually ignored.

The set of rules is in mediawiki/tools/codesniffer.git :
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/tools/codesniffer.git


Reference:
 https://bugzilla.wikimedia.org/show_bug.cgi?id=35588


-- 
Antoine hashar Musso


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test error

[Jeroen De Dauw]

Hey,

I just ran into this issue again by doing a self join somewhere. In the
meanwhile some people pointed out that this 1137 error is caused by MySQL
not supporting more then one reference to a temporary table in a single
query. And we're using temporary tables for running our PHPUnit tests. Is
it possible to change our test stuff to use non-temporary tables?

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test error

[Christian Aistleitner]

Hi Jeroen,

On Fri, Aug 24, 2012 at 06:39:55PM +0200, Jeroen De Dauw wrote:
 Is
 it possible to change our test stuff to use non-temporary tables?

IIRC, you can use the --use-normal-tables option when running the
phpunit tests to avoid using temporary tables.

But of course, this only works locally. You'll have to skip that test
for Jenkins etc. :-(


All the best,
Christian



-- 
 quelltextlich e.U.  \\  Christian Aistleitner 
   Companies' registry: 360296y in Linz
Christian Aistleitner
Gruendbergstrasze 65aEmail:  christ...@quelltextlich.at
4040 Linz, Austria   Phone:  +43 732 / 26 95 63
 Fax:+43 732 / 26 95 63
 Homepage: http://quelltextlich.at/
---


signature.asc
Description: Digital signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test error

[Jeroen De Dauw]

Hey,

 IIRC, you can use the --use-normal-tables option when running the
phpunit tests to avoid using temporary tables.

Awesome, that will work for me :)

 But of course, this only works locally. You'll have to skip that test for
Jenkins etc. :-(

Jenkins is running the tests using SQLite, so the problem does not occur
there.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test error

[Antoine Musso]

Le 10/07/12 21:44, Jeroen De Dauw a écrit :
 Hey,
 
 I got a unit test (added here: https://gerrit.wikimedia.org/r/#/c/14870/)
 causing some error which I can't figure out the cause of.
 
 The error is Error: 1137 Can't reopen table: 'unittest_smw_ids', full
 message here: http://dpaste.org/B2npZ/
 
 Anyone an idea what might be going on?

That is a MySQL bug submitted in May 2005:
 http://bugs.mysql.com/bug.php?id=10327

Test:
  create temporary table tt (x int);
  select * from tt as t1, tt as t2;

Trigger the 1137 error. Basically you cant reference the same temporary
table more than once in the same query :/ Platonides had the issue with
r102411:

http://www.mediawiki.org/wiki/Special:Code/MediaWiki/102411#c29123

The workaround was to skip the query:
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/109024

:(

-- 
Antoine hashar Musso




___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test error

[Jeroen De Dauw]

Hey,

I got a unit test (added here: https://gerrit.wikimedia.org/r/#/c/14870/)
causing some error which I can't figure out the cause of.

The error is Error: 1137 Can't reopen table: 'unittest_smw_ids', full
message here: http://dpaste.org/B2npZ/

Anyone an idea what might be going on?

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test suite for dumping MediaWikis using xmldumps-backup

[Christian Aistleitner]

Hi Saper,

On Sat, Mar 17, 2012 at 09:22:11PM +, Marcin Cieslak wrote:
  Christian Aistleitner christ...@quelltextlich.at wrote:
  [ xmldumps-{backup,test} ]

 Ok so those are two separate pieces of software, [...]

Yes.

 My consfusion came from the fact that I started reading
 README.installation (of -test) that starts with description
 of -backup. 

You are right. Maybe this is too confusing. I'll update the
documentation to make the distinction more obvious.

Kind regards,
Christian



-- 
 quelltextlich e.U.  \\  Christian Aistleitner 
   Companies' registry: 360296y in Linz
Christian Aistleitner
Gruendbergstrasze 65aEmail:  christ...@quelltextlich.at
4040 Linz, Austria   Phone:  +43 732 / 26 95 63
 Fax:+43 732 / 26 95 63
 Homepage: http://quelltextlich.at/
---


signature.asc
Description: Digital signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test suite for dumping MediaWikis using xmldumps-backup

[Marcin Cieslak]

 Christian Aistleitner christ...@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://sa...@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



___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test suite for dumping MediaWikis using xmldumps-backup

[Christian Aistleitner]

Hi Saper,

On Sat, Mar 17, 2012 at 01:59:33PM +, Marcin Cieslak wrote:
  [ Announcing xmldumps-test ]
 
  The code is up for review at
https://gerrit.wikimedia.org/r/p/operations/dumps/test.git

 [ Confusion of URLs and branches ]

yes, the current situation with the ariel branch is suboptimal.

 Which shall we use?

The current xmldumps-test is stored in the master branch of
  https://gerrit.wikimedia.org/r/p/operations/dumps/test.git

The current xmldumps-backup is stored in the ariel branch of
  https://gerrit.wikimedia.org/r/p/operations/dumps.git

(Note the different URLs)

If you find documentation referring to other branches, or other
branches being used anywhere, please let me know.

 [ adding PostgreSQL support ]

As far as I know, xmldumps-backup (the software that xmldumps-test
tests) can only deal with MySQL databases.

However, if you manage to add PostgreSQL support to xmldumps-backup,
adapting xmldumps-test to use PostgreSQL should be doable.

Kind regards,
Christian



-- 
 quelltextlich e.U.  \\  Christian Aistleitner 
   Companies' registry: 360296y in Linz
Christian Aistleitner
Gruendbergstrasze 65aEmail:  christ...@quelltextlich.at
4040 Linz, Austria   Phone:  +43 732 / 26 95 63
 Fax:+43 732 / 26 95 63
 Homepage: http://quelltextlich.at/
---


signature.asc
Description: Digital signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test suite for dumping MediaWikis using xmldumps-backup

[Ariel T. Glenn]

Στις 17-03-2012, ημέρα Σαβ, και ώρα 16:45 +0100, ο/η Christian
Aistleitner έγραψε:
 Hi Saper,
 
 On Sat, Mar 17, 2012 at 01:59:33PM +, Marcin Cieslak wrote:
   [ Announcing xmldumps-test ]
  
   The code is up for review at
 https://gerrit.wikimedia.org/r/p/operations/dumps/test.git
 
  [ Confusion of URLs and branches ]
 
 yes, the current situation with the ariel branch is suboptimal.
 
  Which shall we use?
 
 The current xmldumps-test is stored in the master branch of
   https://gerrit.wikimedia.org/r/p/operations/dumps/test.git
 
 The current xmldumps-backup is stored in the ariel branch of
   https://gerrit.wikimedia.org/r/p/operations/dumps.git

 (Note the different URLs)

I should really move everything over to master soon and use my branch
just for development. Maybe I'll do that before the end of the month.

Ariel





___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Test suite for dumping MediaWikis using xmldumps-backup

[Antoine Musso]

Le 16/03/12 20:02, Christian Aistleitner a écrit :
 The code is up for review at
   https://gerrit.wikimedia.org/r/p/operations/dumps/test.git

And people can browse it using gitweb at:

https://gerrit.wikimedia.org/gitweb/operations/dumps/test.git

Anonymous access:
 https://gerrit.wikimedia.org/r/p/operations/dumps/test.git

Authenticated ssh:
 ssh://gerrit.wikimedia.org:29418/operations/dumps/test.git

-- 
Antoine hashar Musso


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test suite for dumping MediaWikis using xmldumps-backup

[Christian Aistleitner]

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
.
README serves as general point of entry to the documentation.
README.installation shows you how to set up xmldumps-test.
After setup is completed,
 ./run_tests.sh
runs all available tests.

xmldumps-test comes with tests for REL1_1{7,8,9} and trunk.

I'd love to get some feedback, or comments on the scripts.

Best regards,
Christian




-- 
 quelltextlich e.U.  \\  Christian Aistleitner 
   Companies' registry: 360296y in Linz
Christian Aistleitner
Gruendbergstrasze 65aEmail:  christ...@quelltextlich.at
4040 Linz, Austria   Phone:  +43 732 / 26 95 63
 Fax:+43 732 / 26 95 63
 Homepage: http://quelltextlich.at/
---


signature.asc
Description: Digital signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test suite for dumping MediaWikis using xmldumps-backup

[Erik Zachte]

Awesome! I have been looking forward to this QA tool for a long time. 
Presumably this will also shorten dump job suspension after new software
rollouts?!. 

Erik Zachte

-Original Message-
From: wikitech-l-boun...@lists.wikimedia.org
[mailto:wikitech-l-boun...@lists.wikimedia.org] On Behalf Of Christian
Aistleitner
Sent: Friday, March 16, 2012 8:02 PM
To: wikitech-l@lists.wikimedia.org
Subject: [Wikitech-l] Test suite for dumping MediaWikis using
xmldumps-backup

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
.
README serves as general point of entry to the documentation.
README.installation shows you how to set up xmldumps-test.
After setup is completed,
 ./run_tests.sh
runs all available tests.

xmldumps-test comes with tests for REL1_1{7,8,9} and trunk.

I'd love to get some feedback, or comments on the scripts.

Best regards,
Christian




--
 quelltextlich e.U.  \\  Christian Aistleitner 
   Companies' registry: 360296y in Linz Christian
Aistleitner
Gruendbergstrasze 65aEmail:  christ...@quelltextlich.at
4040 Linz, Austria   Phone:  +43 732 / 26 95 63
 Fax:+43 732 / 26 95 63
 Homepage: http://quelltextlich.at/
---


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Test framework update

[Priyanka Dhanda]

Hi,

Here are the notes from a discussion a few of us had a Wikimania. 
Attendees please add anything I may have missed.  Once we make some 
progress on some of the short term goals, we can have another status 
update via phone or Webex.

http://www.mediawiki.org/wiki/Test_framework_07_11_2010

-p

-- 

Priyanka Dhanda
Code Maintenance Engineer
Wikimedia Foundation
http://wikimediafoundation.org

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l