So we are seeing some failures on both the reference build and non-reference build in these tests.  The odd thing is that these jobs are timing out on swarming after 20-30 mins, even though the execution timeout is an hour and a half.  And there seems to be no apparent reason for the time out.  There are benchmark failures, but it should return with exit code 1 and then be reported as a failing step because of the failing benchmarks, not because of a swarming timeout.

One thing to note you will see on the swarming tasks below is that the performance tasks are non existent but maybe that is just due to the timeout on the bot.

Link to most recent swarming battor reference failure, timed out after 22 mins:
https://chromium-swarm.appspot.com/task?id=32eb8f96ef450a10&refresh=10&show_raw=1 


Link to most recent battor swarming non-reference failure, time out after 22 min:
https://chromium-swarm.appspot.com/task?id=32ecdf90dac9a510&refresh=10&show_raw=1



Link to most recent swarming tab_switching reference failure, timed out after 27 mins:
https://chromium-swarm.appspot.com/task?id=32ece68ba3ce7e10&refresh=10&show_raw=1


Link to most recent tab_switching swarming non-reference failure, time out after 27 min:
https://chromium-swarm.appspot.com/task?id=32eb96d9e1f4aa10&refresh=10&show_raw=1




Link to build status page: 
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf

These have been timing out since the 2nd.