All MobileFrontend browsertests Jenkins jobs are failing:
https://integration.wikimedia.org/ci/view/BrowserTests/view/MobileFrontend/
Do you need help fixing the failing jobs? If nobody cares, I will delete failing jobs in a week.
All MobileFrontend browsertests Jenkins jobs are failing:
https://integration.wikimedia.org/ci/view/BrowserTests/view/MobileFrontend/
Do you need help fixing the failing jobs? If nobody cares, I will delete failing jobs in a week.
Ok, no jobs will be deleted. :) Feel fee to reach out to Release-Engineering-Team team if you need help. Also, I have proposed Workshop: Fix broken browsertests/Selenium Jenkins jobs (T94299) for this year's hackathons.
Tests fail for the following reasons
Change 205447 had a related patch set uploaded (by Jdlrobson):
QA: Main menu is now a nav
Change 205448 had a related patch set uploaded (by Jdlrobson):
QA: Fix failing VisualEditor test due to toolbar changes
Change 205450 had a related patch set uploaded (by Jdlrobson):
Don't expose the toggling init function
Change 205451 had a related patch set uploaded (by Jdlrobson):
QA: Fix the browser tests to reflect anonymous editing on beta labs
Change 205451 merged by jenkins-bot:
QA: Fix the browser tests to reflect anonymous editing on beta labs
Change 205448 merged by jenkins-bot:
QA: Remove failing VisualEditor test due to toolbar changes
Logged in with my LDAP account, I have manually triggered runs for the three browser tests jobs at https://integration.wikimedia.org/ci/view/BrowserTests/view/MobileFrontend/
Once completed, should get us results on:
That last job passed overnight so I guess it is a good indication the patches fixed something :-)
Reopening since the builds I triggered earlier have some failures. The trend shows a large improvement though!
Wait, not all MobileFrontend Jenkins jobs are fixed:
https://integration.wikimedia.org/ci/view/BrowserTests/view/MobileFrontend/
All MobileFrontend jobs are broken again. :/
https://integration.wikimedia.org/ci/view/BrowserTests/view/MobileFrontend/
Feel free to create subtasks.
Change 269751 had a related patch set uploaded (by Phuedx):
Make SchemaEdit#log always return jQuery.Promise
Change 269755 had a related patch set uploaded (by Alex Monk):
Make SchemaEdit#log always return jQuery.Promise
Change 269751 merged by jenkins-bot:
Make SchemaEdit#log always return jQuery.Promise
Change 269848 had a related patch set uploaded (by Jforrester):
Make SchemaEdit#log always return jQuery.Promise
The remaining tests are failing with "Net::ReadTimeout (Net::ReadTimeout)"
The watchlist feature is fine so these seem to be false positives. @zeljkofilipin your team is likely to be better equipped to get to the bottom of these problems.
https://integration.wikimedia.org/ci/view/BrowserTests/view/MobileFrontend/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/955/
@Jdlrobson: the only way we can make test maintenance sustainable is to teach you how to fix them. If anybody from your team wants to pair on fixing the tests, my calendar is always up to date. I do not want to volunteer @dduvall, but he also knows how to fix tests. You will have to check with him if he is available.
Change 274357 had a related patch set uploaded (by Zfilipin):
Disable scenarios that fail at en.wikipedia.beta.wmflabs.org from running daily
Change 277821 had a related patch set uploaded (by Jdlrobson):
Specify Special:EditWatchlist in watchlist switching tests
The thing that is strange is Sauce Labs seems to be navigating to Special:Watchlist via the hamburger menu. Is there a rule in one of the libraries that could be being used instead of the one in MobileFrontend?
I am on the "Special:Watchlist" page
seems to be invoking the
I click on "Watchlist" in the main navigation menu
step but it shouldn't be.
Change 277821 merged by jenkins-bot:
Specify Special:EditWatchlist in watchlist switching tests
Change 274357 merged by jenkins-bot:
Disable scenarios that fail at en.wikipedia.beta.wmflabs.org from running daily
They are more or less passing now except a few occasions of flakey failures in the Firefox build.