Is there any way we can flag these related bugs in the report itself, so
when someone glances at the e-mail they know it might be due to a related
bug and not a regression?
I guess we could at least document the test itself in the code to link it
to the bug...
On Tue, Jan 28, 2014 at 10:21 AM, Chris McMahon <cmcmahon(a)wikimedia.org>wrote;wrote:
sometimes Chrome never gets a starting URL. tracking this issue here:
https://bugzilla.wikimedia.org/show_bug.cgi?id=60338
On Tue, Jan 28, 2014 at 11:13 AM, Jon Robson <jrobson(a)wikimedia.org>wrote;wrote:
Any ideas on why this one would fail - is this a
timeout?
On Mon, Jan 27, 2014 at 4:40 PM, <jenkins-no-reply(a)cloudbees.com> wrote:
* FAILURE:
MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome Build #226
<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome/226/>
(Tue, 28 Jan 2014 00:20:50 +0000)*
*Test
Result*<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.b…
1 failed, 5 skipped
Failed Tests *Test Name**Duration**Age* Menus open correct
page.Settings URL is set
correctly<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia…
12
sec1<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta…
All
Tests *Package**Duration**Fail**Skip**Total*
(
root)<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.bet…
min1551
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l