I'm not sure how this is happening but a Vector browser test introduced by Ib153f1d55e4471c4dc1e16ad3c9ae0ea9f73acf5 is running on Minerva and possibly other skins.
This is blocking merges in the repo... as we cannot manually override the "Verified +2" in that repo.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Revert "Move Selenium test from mediawiki/core" | mediawiki/skins/Vector | master | +0 -96 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | zeljkofilipin | T182986 Selenium framework improvements | |||
| Resolved | zeljkofilipin | T190995 Someday/maybe Selenium framework improvements | |||
| Resolved | zeljkofilipin | T185928 New usermessage browser test is blocking merges in Minerva skin and Echo extension | |||
| Resolved | zeljkofilipin | T187859 Move one Selenium tests from mediawiki/core to mediawiki/skins/Vector | |||
| Resolved | zeljkofilipin | T188553 Vector browser test blocking merge in Minerva |
Easiest thing to do would be to revert - https://gerrit.wikimedia.org/r/#/c/415393/
@zeljkofilipin I have no idea why Vector's browser tests are running on Minerva so ideally we'd fix that instead. Do you have any ideas? Ideally only the browser tests for the current skin should be running.
https://integration.wikimedia.org/ci/job/mediawiki-core-qunit-selenium-jessie/15723/console
20:35:34 10 passing (79.30s)
20:35:34 1 failing
20:35:34
20:35:34 1) User should be able to view new message banner:
20:35:34 An element could not be located on the page using the given search parameters ("div.usermessage").
20:35:34 running chrome
20:35:34 Error: An element could not be located on the page using the given search parameters ("div.usermessage").
20:35:34 at elements() - getText.js:18:17
20:35:34 at getText() - at Context.<anonymous> (skins/Vector/tests/selenium/specs/user.js:41:45)@zeljkofilipin have spent much of today looking into this but can't work out what's going on. Hopefully can sync with you tomorrow to resolve this, if not I think we'll have to revert the patch until we work this out.
@Jdlrobson why is mediawiki-core-qunit-selenium-jessie job running for Minerva, since it does not have Selenium tests?
Our Selenium framework is set up to run all tests it can find (wdio.conf.js). I did not know that CI jobs always clone Vector skin. So, when the test was merged there, it started running Vector tests even for commits in Minerva (example: 415373).
Resolved by 415393.
I have talked with @hashar about it, there are several ways we can fix the problem in CI. The work will continue in original task, T187859.