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 <> wrote:

sometimes Chrome never gets a starting URL. tracking this issue here:

On Tue, Jan 28, 2014 at 11:13 AM, Jon Robson <> wrote:
Any ideas on why this one would fail - is this a timeout?

On Mon, Jan 27, 2014 at 4:40 PM, <> wrote:
FAILURE: Build #226 (Tue, 28 Jan 2014 00:20:50 +0000)

Test Result

1 failed, 5 skipped

Failed Tests

Test NameDurationAge
Menus open correct page.Settings URL is set correctly 12 sec1

All Tests

(root)13 min1551

Mobile-l mailing list