On Mon, Jan 13, 2014 at 12:11 PM, Arthur Richards <arichards@wikimedia.org> wrote:

On Mon, Jan 13, 2014 at 11:57 AM, Jon Robson <jrobson@wikimedia.org> wrote:
What could cause such a blip?

About a million different things :p A lot of teams use betalabs, and betalabs runs on labs infrastructure - so there are a ton of variables that can easily go sideways and cause weirdness/breakage on betalabs.

I've written an overview of the architecture here:  http://www.mediawiki.org/wiki/Browser_testing/architecture

For this particular instance, if you click the link in the email sent to you from Jenkins it sends you to the page at: 
ps://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome/191/testReport/junit/(root)/Menus%20open%20correct%20page/Uploads_URL_is_set_correctly/

When you click on the link from that page to the failure in Sauce Labs it shows the page at: 
https://saucelabs.com/jobs/ac9a75b2f2cf4a61b7247ed6df5ab91c

Where the last thing Chrome reported is "No data received"

To recap: click the link in the email; click the link to the Sauce Labs job; see the last screenshot; if you need more info, click the "Screencast" tab to see the replay of the entire test. 


 
 
Is there any way to distinguish better between blips and real errors (as I spent 10 minutes verifying if this was broken or not)

I check to see if subsequent tests have also been failing or if they passed.

--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr