The lack of replies from any mobile team members seems to suggest I'm the only one watching this. In that case I'd rather we split up the big MobileFrontend job into various jobs based on certain features. How can we get more people caring about browser tests? Naming and shaming?

Practically, the current big job [1] we have has far too many false positives and it is just noise to me. I was paying attention to the smoke tests [2] but I was told that was an upstream bug and haven't been watching it since. Any idea why that has been failing recently? Nothing has broken here...

[1] https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/
[2] https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFrontend-SmokeTests-linux-chrome-sauce/

On Thu, Mar 26, 2015 at 3:32 AM, Antoine Musso <hashar+wmf@free.fr> wrote:
On 25/03/15 21:37, Greg Grossmeier wrote:
Does the mobile team have the browser test pass/failure announcements
sent to it's IRC channel now?

The MobileFrontend jobs send emails to chris and qa-alerts . It is configured JJB integration/config.git /jjb/browsertests.yaml via YAML aliases [1].

The project 'MobileFrontend' has:

  recipients: *emails-qa

One would need to define a new alias for Mobile at the top of the file. Maybe the mobile team as an alert


IRC notifications are only send to #wikimedia-releng. It needs a bit more work to get make it customizable.


[1] https://git.wikimedia.org/blob/integration%2Fconfig/0b91d99/jjb%2Fbrowsertests.yaml


--
Antoine Musso


_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l



--
Jon Robson
* http://jonrobson.me.uk
* https://www.facebook.com/jonrobson
* @rakugojon