[QA] Quibble test runner version 0.0.40 released

All, I've released a new version of Quibble just today, version 0.0.40. This has a few changes, most notable further improvements to support the work on testing Core Platform team's new RESTful API. The full change log is available at https://doc.wikimedia.org/quibble/changelog.html Thank you

Re: [QA] Proposal to close this list

On Wed, 30 Oct 2019 at 03:47, Željko Filipin wrote: > Hi, > > I propose to close this list. I don't think it has any purpose. > > Group description[0] points to a page that is obsolete[1]. Archives[2] say > that there's just a few announcements a month. There are no discussions. > > I think all

[QA] FYI: Continuous Integration now running node 10 for MW, extensions, and skins

Hey all, A quick heads-up: the continuous integration tests for MediaWiki core, MediaWiki extensions, and MediaWiki skins are now all using node 10, replacing node 6, which is end-of-life. CI jobs were replaced by new ones which should run faster, without any disruption for developers' work. For

Re: [QA] CI update to Chromium 63

On Fri, 15 Dec 2017 at 08:11 Antoine Musso wrote: > Hello, > > Most of the npm test jobs are now running on Docker. On Monday I will > upgrade the Docker container to use Chromium 63 instead of 62. > > Non npm jobs (eg Mediawiki QUnit tests) are still on Jessie with >

[QA] FYI: CI npm version upgraded from 2.x to 3.x

Please note that we've upgraded the version of npm used in the Wikimedia continuous integration infrastructure. This means that CI should be more consistent with developers' local set-ups, and lets us test in a more normal environment. This change will only affect node-based CI tasks, like the

Re: [QA] Why is puppet on deployment-sca-cache01 disabled?

On 18 December 2014 at 06:10, Antoine Musso hashar+...@free.fr wrote: Le 18/12/2014 09:11, Yuvi Panda a écrit : Has been for about 6 days, is that still intentional? While at it, does anyone have any idea what this instance is for? ​SCA == Services Cluster A. It's for miscellaneous things

Re: [QA] Merging CI configuration repos

On Tuesday, October 7, 2014, Željko Filipin zfili...@wikimedia.org wrote: On Tue, Oct 7, 2014 at 3:58 PM, Antoine Musso hashar+...@free.fr javascript:_e(%7B%7D,'cvml','hashar%2b...@free.fr'); wrote: Thoughts? +1! :) +1; co-ordinating has been a pain. That said, normal practice as I

Re: [QA] Beta Labs code update failing again (for ~ 6 hours)

On 11 September 2014 08:56, Bryan Davis bd...@wikimedia.org wrote: On Wed, Sep 10, 2014 at 11:20 PM, Bryan Davis bd...@wikimedia.org wrote: On Wed, Sep 10, 2014 at 9:27 PM, James Forrester jforres...@wikimedia.org wrote: https://bugzilla.wikimedia.org/show_bug.cgi?id=70696 Looks

Re: [QA] Problem with Selenium, MobileFrontend, or VisualEditor?

On 8 September 2014 10:17, Željko Filipin zfili...@wikimedia.org wrote: On Mon, Sep 8, 2014 at 5:36 PM, Chris McMahon cmcma...@wikimedia.org wrote: What's happening is that Selenium is trying to enter a string into the ContentEditable div in VisualEditor manifested within the MobileFrontend

[QA] Beta Labs synchronising down

Beta Labs isn't synchronising; AFAICS it hasn't done so since ~ 11 hours ago (15:10 UTC on 2014-09-08). I noticed this when prepping a patch for tomorrow and found that. Going to https://integration.wikimedia.org/ci/view/Beta/ I found that beta-update-databases-eqiad had been executing for 12

Re: [QA] Browser tests dashboard on Jenkins

On 22 August 2014 04:19, Antoine Musso hashar+...@free.fr wrote: Hello, S has filled [bug 67332] to request per project dashboards/view in Jenkins. I gave it a shot this morning and came up with: - A dashboard view (default) - A catch all view '-All' which shows all jobs - CirrusSearch

Re: [QA] Prettier Jenkins results in Gerrit

On 20 August 2014 13:02, Antoine Musso hashar+...@free.fr wrote: Hello, The tests results being reported to Gerrit are now much nicer. The first ever example is https://gerrit.wikimedia.org/r/#/c/155341/ James E. Blair from Openstack found a nice trick to inject HTML in Gerrit comment.

Re: [QA] Two big improvements for flaky tests

On 25 July 2014 09:29, Chris McMahon cmcma...@wikimedia.org wrote: This month we've made two big improvements that should greatly reduce the number of flaky test failures in all of the builds. For one thing, the MobileFrontend test that used to walk through a dozen steps to protect a page

Re: [QA] beta cluster is too busy

On 22 July 2014 09:24, Antoine Musso hashar+...@free.fr wrote: Hello, Yesterday a patch landed in MediaWiki core that causes the database update script to update a bunch of tables and do a lot of queries on the database. The slave database is thus lagged out by 4+ hours as I write this and

Re: [QA] Failing MobileFrontend browser tests

On 14 July 2014 06:44, Željko Filipin zfili...@wikimedia.org wrote: On Sat, Jul 12, 2014 at 12:50 AM, James Forrester jforres...@wikimedia.org wrote: ​Steps (I had to do this last week; sharing the learning rather than just replicating the issue): 1. ​Go​ to https

Re: [QA] Failing MobileFrontend browser tests

On 11 July 2014 15:19, Arthur Richards aricha...@wikimedia.org wrote: Greg, Rob, Tomasz and I just had an IRL conversation about this. Given some of the ambiguity of the test failures we've been discussing as related to 'infrastructure/architecture issues', we should be filing specific bug

Re: [QA] Moving builds off Cloudbees: VisualEditor, MobileFrontend, Flow

On Monday, June 30, 2014, S Page sp...@wikimedia.org wrote: On Mon, Jun 30, 2014 at 4:43 PM, Chris McMahon cmcma...@wikimedia.org javascript:_e(%7B%7D,'cvml','cmcma...@wikimedia.org'); wrote: I'm not sure what happened here either. Right now Flow tests are not handling Close and Open

Re: [QA] future of gadget tests from qa/browsertest repo

On 30 June 2014 08:56, Chris McMahon cmcma...@wikimedia.org wrote: We have two tests in the /qa/browsertests repo, and Matt wants to know what is going to happen to them: https://gerrit.wikimedia.org/r/#/c/142359/ Tests for gadget certainly don't belong in /mediawiki/core. Since gadgets

Re: [QA] Moving builds off Cloudbees: VisualEditor, MobileFrontend, Flow

On 17 June 2014 09:53, Chris McMahon cmcma...@wikimedia.org wrote: On Mon, Jun 16, 2014 at 10:57 AM, James Forrester jforres...@wikimedia.org wrote: Chris, Željko, Thank you so much, this is great; is there anything I can do to help move over the remaining VE browser tests? The only VE

Re: [QA] Moving builds off Cloudbees: VisualEditor, MobileFrontend, Flow

Chris, Željko, Thank you so much, this is great; is there anything I can do to help move over the remaining VE browser tests? J. On 16 June 2014 09:26, Chris McMahon cmcma...@wikimedia.org wrote: Hi all, After some doing some spikes last week, Željko and I moved our first six official

Re: [QA] Moving builds off Cloudbees: VisualEditor, MobileFrontend, Flow

Chris, Thanks. :-) J. On 16 June 2014 11:04, Chris McMahon cmcma...@wikimedia.org wrote: On Mon, Jun 16, 2014 at 10:57 AM, James Forrester jforres...@wikimedia.org wrote: Chris, Željko, Thank you so much, this is great; is there anything I can do to help move over the remaining VE

Re: [QA] VE build run on SauceLabs via WMF Jenkins

On 9 June 2014 09:18, Chris McMahon cmcma...@wikimedia.org wrote: Željko and I (mostly Željko!) got this running today: https://saucelabs.com/tests/e580fcbe2d5745d59f37600c6e0e9015 Still more config and refactoring work to do in Jenkins Job Builder, but this is pretty great. It has been a

Re: [QA] [EE] migrating Flow tests to WMF Jenkins

On 6 June 2014 16:21, Chris McMahon cmcma...@wikimedia.org wrote: On Fri, Jun 6, 2014 at 4:16 PM, Matthew Flaschen mflasc...@wikimedia.org wrote: Are they voting or non-voting? I think browser tests should always be non-voting. Therein lies a day-long training session... ​And FWIW I

Re: [QA] [WikimediaMobile] MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox - Build # 509 - Still Failing!

On 22 April 2014 11:08, Bryan Davis bda...@wikimedia.org wrote: On Tue, Apr 22, 2014 at 11:54 AM, Arthur Richards aricha...@wikimedia.org wrote: Huh could be - I could've sworn betalabs showed specific SHA1s of extensions on Special:Version previously, but it currently does not so I'm not

Re: [QA] Browsertests using only WMF Jenkins and beta labs!

On 18 April 2014 11:12, Greg Grossmeier g...@wikimedia.org wrote: quote name=Chris McMahon date=2014-04-18 time=10:26:35 -0700 Hello QAers, Thanks to Antoine and Željko, we are now running a number of builds for browsertests that use the WMF Jenkins instance with headless Firefox to run

Re: [QA] Overhauling 'recheck' in Gerrit

On 16 April 2014 13:24, Antoine Musso hashar+...@free.fr wrote: Hello, TL;DR: make 'recheck' by a whitelisted user to triggers tests jobs Gerrit/Zuul have a hidden feature which is that one can comment 'recheck' on a change in Gerrit and that reenqueue the Change in the Zuul 'check'

Re: [QA] My last day at WMF

Jeff, So sorry that you're going; you've been a huge asset to the team, and we'll really miss you. The work you've done on improving our automated tests for VisualEditor has been awesome, and massively helpful. Best of luck in the future. J. On 20 February 2014 09:05, Jeff Hall

Re: [QA] Browser tests for VisualEditor accessed via the Mobile interface

On 17 January 2014 04:38, Jeff Hall jh...@wikimedia.org wrote: During this morning's VisualEditor team meeting, James Forrester mentioned that we should start developing browser tests for VisualEditor accessed via the Mobile interface (as opposed to existing browser tests for VE accessed via

Re: [QA] Jenkins cleanup

On 27 August 2013 04:03, Željko Filipin zfili...@wikimedia.org wrote: On Tue, Aug 27, 2013 at 12:34 PM, Željko Filipin zfili...@wikimedia.orgwrote: Today I have moved ULS[1] tests from browsertests[2] repository to ULS repository[3]. This is actually a Big Thing. ULS is the third