In T167432#3366736, @Aleksey_WMDE wrote:

Any update on when you will be able to start working on this ticket?

In T164721#3368608, @Jdlrobson wrote:

I personally don't use Vagrant.

I have updated the docs in the above patch. It is no longer needed to use bundler < 1.8 I have tested it with the latest release 1.15.1.

Looks like this is already resolved in 43e3a40a68e9e79868008d4276df90f199d44ff9 by @hashar.

In T164721#3355289, @Jdlrobson wrote:

The purpose is only for browser tests. The vagrant role shouldn't do this.

@Jdlrobson I have added

I have found how Ruby CI does it in mw-selenium-setup.sh.

In T164721#3349109, @Jdlrobson wrote:

@zeljkofilipin are you including LocalSettings.php?
I mentioned this before.. the LocalSettings.php in tests/browser needs to be included by the job and locally for the tests to work:

include_once "$IP/extensions/RelatedArticles/tests/browser/LocalSettings.php";

As far as I know, nothing has changed recently. @hashar could know more.

Looks like @Jdlrobson's patch is running fine in CI:

@hashar thanks, I have already figured that out :)

Ah, the docs for Extension:RelatedArticles says:

In T164721#3345389, @zeljkofilipin wrote:

The job (mediawiki-core-qunit-selenium-jessie/2545) fails with element (.ext-cards-card) still not existing after 2000ms but it fails the same way on my machine. I guess something changed in the implementation.

TLDR: mediawiki-core-qunit-selenium-jessie runs for RelatedArticles in experimental pipeline.

The above patch fixes the problem for phantomjs 2.1.1. The problem is still reproducible with phantomjs 1.9.7 that is installed at cirrus-browser-bot. Is there a reason cirrus-browser-bot is locked to 1.9.7? Can you upgrade?

@pmiazga apologies for the delay, I have to finish some selenium+node tasks before I can get back to this.

Apologies for the delay, I will be working on it this week.

The screenshots taking part works fine now. I will work on the uploading images to commons after I resolve some urgent tasks.

Will work on this after T164721 is resolved.

This is blocked until T164721 is resolved.

Reproduced on my machine, targeting mediawiki-vagrant:

As I said in the previous comment, the script works just fine targeting https://en.wikipedia.org/wiki/Help:Sample_page. I am not sure why the pages in article namespace are needed @Jeff_G?

I am not sure that the articles are needed. Currently the script works just fine targeting https://en.wikipedia.org/wiki/Help:Sample_page.

Apologies with the delay, I was distracted with other work. This should be done early next week.

I have talked with @hashar about this. I can take this task as soon as I have finished a few that I am already working on.

Deleting node_modules folder and running npm install fixed the problem.

The workaround is to downgrade to node 6.

Looks related: https://github.com/webdriverio/wdio-mocha-framework/issues/30

In T162966#3304112, @EBernhardson wrote:

we actually setup cirrus-browser-bot.eqiad.wmflabs because it tends to run lots faster than a local mediawiki-vagrant install.

In T94001#3246240, @Mattflaschen-WMF wrote:

The footer looks good now, except the license links are broken.

mediawiki-ruby-api goes to https://doc.wikimedia.org/rubygems/LICENSE.txt and mediawiki-selenium goes to https://doc.wikimedia.org/rubygems/LICENSE , and both 404.