Re: [QA-Alerts] selenium-GettingStarted » firefox,beta,Linux,BrowserTests - Build # 901 - Failure!

2018-09-24 Thread Sam Smith
This appears to be caused by https://phabricator.wikimedia.org/T172560. -Sam ___ QA-Alerts mailing list QA-Alerts@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/qa-alerts

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,BrowserTests - Build # 673 - Still Failing!

2017-12-31 Thread Sam Smith
This has been fixed. Happy New Year  -Sam ___ QA-Alerts mailing list QA-Alerts@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/qa-alerts

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,BrowserTests - Build # 673 - Still Failing!

2017-12-26 Thread Sam Smith
o/ Firstly, I hope y'all are having good holidays. Fortunately (or unfortunately), this browser test has picked up what looks like a regression. It's likely caused by the recent Multi-Content Revision work that was merged into core on December, 21st ([0] onwards). The reason I point to this

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,BrowserTests - Build # 562 - Still Failing!

2017-09-19 Thread Sam Smith
Done <https://phabricator.wikimedia.org/T176222>. -Sam --- Engineering Manager Readers Timezone: BST (UTC+1) IRC (Freenode): phuedx Matrix: @phuedx:matrix.org On Tue, Sep 19, 2017 at 4:41 PM, Sam Smith <samsm...@wikimedia.org> wrote: > You have been blocked from ed

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,BrowserTests - Build # 562 - Still Failing!

2017-09-19 Thread Sam Smith
> > You have been blocked from editing. (blocked) (MediawikiApi::ApiError) I'll create a task. -Sam ___ QA-Alerts mailing list QA-Alerts@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/qa-alerts

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,BrowserTests - Build # 459 - Failure!

2017-06-19 Thread Sam Smith
These appear to be Sauce Labs failures. [image: 落] -Sam --- Journeyman Software Engineer, Expert Beard Grower IRC (Freenode): phuedx Timezone: BST (UTC+1) ___ QA-Alerts mailing list QA-Alerts@lists.wikimedia.org

Re: [QA-Alerts] selenium-GettingStarted » firefox,beta,Linux,BrowserTests - Build # 374 - Still Failing!

2017-04-24 Thread Sam Smith
Looks like it's not been fixed. Does the Redis instance in eqiad need to be populated with the maintenance script? -Sam On Fri, Apr 21, 2017 at 8:56 PM, Matthew Flaschen wrote: > I think this will be fixed by https://gerrit.wikimedia.org/r/#/c/349349/ > (regression due

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,BrowserTests - Build # 352 - Failure!

2017-03-08 Thread Sam Smith
False positive: the Beta Cluster fell over in the middle of these tests. -Sam On Wed, Mar 8, 2017 at 8:22 PM, jenkins-bot wrote: > * FAILURE: > BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=BrowserTests > Build #352 >

Re: [QA-Alerts] selenium-MobileFrontend - Build # 351 - Failure!

2017-03-08 Thread Sam Smith
It's always good when there's no Sauce Labs job URL isn't it? Given that the first test failed in 5 seconds, I think that this is a false negative. The Page diff test, however, is a repeat offender and fixing it was tracked in T144300: Page diff test failing

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 326 - Failure!

2017-02-14 Thread Sam Smith
There isn't a Sauce Labs job URL so it's hard to see what might be causing this failure. My guess is that the BC was particularly slow during this test. -Sam On Wed, Feb 15, 2017 at 1:56 AM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] selenium-GettingStarted » firefox,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 275 - Still Failing!

2017-01-17 Thread Sam Smith
It's not immediately obvious why this browser test is failing. Indeed, I can go through the create-account-see-getting-started-modal workflow on the Beta Cluster without fail. -Sam On Tue, Jan 17, 2017 at 4:23 AM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 265 - Failure!

2016-12-20 Thread Sam Smith
This failure was caused by Sauce Labs being unable to start a VM . -Sam On Mon, Dec 19, 2016 at 3:51 PM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 262 - Failure!

2016-12-16 Thread Sam Smith
This failure seems to have been caused by the Beta Cluster being a little slow. -Sam On Fri, Dec 16, 2016 at 3:45 PM, jenkins-bot wrote: > * FAILURE: > BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=contintLabsSlave > && UbuntuTrusty Build #262 >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 257 - Failure!

2016-12-12 Thread Sam Smith
It looks like Sauce Labs was at fault here. -Sam On Sun, Dec 11, 2016 at 3:43 PM, jenkins-bot wrote: > * FAILURE: > BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=contintLabsSlave > && UbuntuTrusty Build #257 >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 231 - Failure!

2016-11-18 Thread Sam Smith
It looks as if the Beta Cluster fell over after the first step of the test. The API responded with an HTTP 503 Service Unavailable. -Sam On Thu, Nov 17, 2016 at 3:42 PM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 226 - Failure!

2016-11-14 Thread Sam Smith
Under what conditions should this test pass? -Sam On Sun, Nov 13, 2016 at 3:42 PM, jenkins-bot wrote: > * FAILURE: > BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=contintLabsSlave > && UbuntuTrusty Build #226 >

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 222 - Failure!

2016-11-10 Thread Sam Smith
This looks like the languages query took too long. Perhaps we could make this more resilient by ensuring that the overlay is visible? -Sam On Wed, Nov 9, 2016 at 3:53 PM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] selenium-GettingStarted » firefox,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 176 - Failure!

2016-10-14 Thread Sam Smith
This failure was caused by T148111: DBQueryError when creating account on Beta, or logging into newly-created accounts . -Sam On Fri, Oct 14, 2016 at 1:22 PM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 191 - Failure!

2016-10-13 Thread Sam Smith
-Sam On Thu, Oct 13, 2016 at 1:19 PM, Sam Smith <samsm...@wikimedia.org> wrote: > This was caused by Ie9dafeb3: Always remember your wg prefix > <https://gerrit.wikimedia.org/r/#/c/315450/> and I1ac60838: Disable > bottom language button in Minerva > <https://gerrit

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 191 - Failure!

2016-10-13 Thread Sam Smith
This was caused by Ie9dafeb3: Always remember your wg prefix and I1ac60838: Disable bottom language button in Minerva . -Sam On Wed, Oct 12, 2016 at 4:38 PM, jenkins-bot wrote: >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 185 - Failure!

2016-10-07 Thread Sam Smith
Wait… This is Footer V2 ain't it? -Sam On Fri, Oct 7, 2016 at 6:22 PM, Sam Smith <samsm...@wikimedia.org> wrote: > These appear to be genuine regressions. mobile.modifiedBar appears to be > playing up on the Beta Cluster, at least. > > -Sam > > On Fri, Oct 7, 2016

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 185 - Failure!

2016-10-07 Thread Sam Smith
These appear to be genuine regressions. mobile.modifiedBar appears to be playing up on the Beta Cluster, at least. -Sam On Fri, Oct 7, 2016 at 4:38 PM, jenkins-bot wrote: > * FAILURE: > BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=contintLabsSlave >

Re: [QA-Alerts] selenium-GettingStarted - Build # 166 - Failure!

2016-10-04 Thread Sam Smith
This is most probably caused by T147240: LoadBalancer fatals on Beta cluster rendering pages inaccessible . -Sam On Tue, Oct 4, 2016 at 1:22 PM, jenkins-bot wrote: > * FAILURE: selenium-GettingStarted Build #166 >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 174 - Still Failing!

2016-09-30 Thread Sam Smith
They "User:.Check user page is editable" is failing because the user's page exists. We should either delete the page at the start of the scenario: Given I haven't created my user page Or we could use the mediawiki-selenium's user factory for this scenario, i.e. log in as a new user time every

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 156 - Still Failing!

2016-09-14 Thread Sam Smith
All tests that log the user are failing: Mediawiki::Client#login appears to be receiving 403 Forbidden responses from the API. Anyone know what might've caused this? -Sam On Tue, Sep 13, 2016 at 4:27 PM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 143 - Still Failing!

2016-09-01 Thread Sam Smith
Has anyone investigated these failures? -Sam On Thu, Sep 1, 2016 at 4:39 PM, jenkins-bot wrote: > * FAILURE: > BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=contintLabsSlave > && UbuntuTrusty Build #143 >

Re: [QA-Alerts] selenium-GettingStarted - Build # 109 - Failure!

2016-08-10 Thread Sam Smith
Is this because the CAPTCHA input isn't being filled? Unfortunately, the screencast is at too low a resolution to see whether or not this is the case. -Sam On Wed, Aug 10, 2016 at 1:22 PM, jenkins-bot wrote: > * FAILURE: selenium-GettingStarted Build #109 >

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 104 - Still Failing!

2016-08-03 Thread Sam Smith
Writes via the API are failing during integration but not when I test directly on the Beta Cluster. Any ideas? -Sam On Wed, Aug 3, 2016 at 4:38 PM, jenkins-bot wrote: > * FAILURE: > BROWSER=firefox,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=contintLabsSlave >

Re: [QA-Alerts] selenium-MobileFrontend - Build # 102 - Still Failing!

2016-08-02 Thread Sam Smith
I can only assume that this is the API failing *hard*, i.e. an exception not being caught, and then the API client trying to parse it as JSON. I've moved T141647 back into *-1 (Needs More Work)*. -Sam On Wed, Aug 3, 2016 at 6:20 AM, jenkins-bot wrote: > * FAILURE:

Re: [QA-Alerts] selenium-MobileFrontend » firefox,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 95 - Still Failing!

2016-07-29 Thread Sam Smith
This is worth checking out … These tests passed locally and on the Jenkins build slaves on a per-commit basis. I suspect I botched the change to tests/browser/LocalSettings.php in Ie11a32b . -Sam On Fri, Jul 29, 2016

Re: [QA-Alerts] selenium-MobileFrontend » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 65 - Still Failing!

2016-07-01 Thread Sam Smith
It looks as if the wikitext editor modules didn't load within 5 seconds and the test failed. Given the step definition, I'd say that this is a genuine failure but, since I can use the wikitext editor locally and on http://en.m.wikipedia.beta.wmflabs.org, it isn't a regression. Thoughts? -Sam On

Re: [QA-Alerts] selenium-QuickSurveys » chrome,beta,Linux,contintLabsSlave && UbuntuTrusty - Build # 53 - Failure!

2016-06-14 Thread Sam Smith
The Beta Cluster was in read-only mode for both of these scenarios. -Sam On Tue, Jun 14, 2016 at 3:14 AM, jenkins-bot wrote: > * FAILURE: > BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=Linux,label=contintLabsSlave > && UbuntuTrusty Build #53 >

Re: [QA-Alerts] browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce - Build # 1058 - Failure!

2016-04-27 Thread Sam Smith
This is a false negative. The Beta Cluster fell over during the test. -Sam On Wed, Apr 27, 2016 at 4:13 AM, jenkins-bot wrote: > * FAILURE: > browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce > Build #1058 >

Re: [QA-Alerts] selenium-MobileFrontend - Build # 11 - Still Failing!

2016-04-01 Thread Sam Smith
404 Not Found for every link to a failed test. Is this an April Fools' Day prank RelEng? -Sam On Fri, Apr 1, 2016 at 4:54 PM, jenkins-bot wrote: > * FAILURE: selenium-MobileFrontend Build #11 > >

Re: [QA-Alerts] browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce - Build # 976 - Still Failing!

2016-02-14 Thread Sam Smith
The CirrusSearch exception that caused these three failures is tracked by T126672 – thanks for creating the task JR! -Sam On Mon, Feb 15, 2016 at 3:21 AM, jenkins-bot wrote: > * FAILURE: >

Re: [QA-Alerts] browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce - Build # 946 - Still Failing!

2016-02-10 Thread Sam Smith
The beta-scap-eqiad job last succeeded 23 hours ago so MobileFrontend isn't up to date. The Wikitext Editor failures were fixed during T126497 . The "Check links in menu" test failure is tracked in T126466 .

Re: [QA-Alerts] browsertests-MobileFrontend-SmokeTests-linux-chrome-sauce - Build # 389 - Still Failing!

2016-01-19 Thread Sam Smith
This looks like the a BC failure at first glance but the "Age: 5" worries me. Investigating… On Tue, Jan 19, 2016 at 2:37 PM, jenkins-bot wrote: > * FAILURE: browsertests-MobileFrontend-SmokeTests-linux-chrome-sauce Build > #389 >

Re: [QA-Alerts] browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce - Build # 927 - Still Failing!

2015-12-30 Thread Sam Smith
This is indeed regression, caused by the introduction of the MobileFrontend\MenuBuilder class and fixed in I03e4403 . On Wed, Dec 30, 2015 at 3:26 AM, jenkins-bot wrote: > * FAILURE: >