Performance dashboard identified a zero-to-nonzero regression in graphics_WebGLPerformance/Failures on cros-veyron_mickey at revision range 32180000995900001:32180000996100000. Graph: https://chromeperf.appspot.com/report?masters=ChromeOS_Graphics&bots=cros-veyron_mickey&tests=graphics_WebGLPerformance%2FFailures&checked=Failures%2CFailures_ref%2Cref&rev=32180000996100000

ChromeOS Version range: 63.9959.0.0 - 63.9961.0.0 
Chrome Version: 63.0.3218.0 

https://crosland.corp.google.com/log/9959.0.0..9961.0.0
https://omahaproxy.appspot.com/changelog?old_version=63.0.3218.0&new_version=63.0.3218.0

This may be related to crbug.com/768400.  However, so far this looks ARM-specific and the graph implies a Chrome change is not a fault.  Assigning to current GFX guard for investigation, though I would wait until the cause of crbug.com/768400 is determined.
 

Performance dashboard identified a zero-to-nonzero regression in graphics_WebGLPerformance/Failures on cros-veyron_mickey at revision range 32180000995900001:32180000996100000. Graph: https://chromeperf.appspot.com/report?masters=ChromeOS_Graphics&bots=cros-veyron_mickey&tests=graphics_WebGLPerformance%2FFailures&checked=Failures%2CFailures_ref%2Cref&rev=32180000996100000

ChromeOS Version range: 63.9959.0.0 - 63.9961.0.0 
Chrome Version: 63.0.3218.0 

https://crosland.corp.google.com/log/9959.0.0..9961.0.0
https://omahaproxy.appspot.com/changelog?old_version=63.0.3218.0&new_version=63.0.3218.0

This may be related to crbug.com/768400.  However, so far this looks ARM-specific and the graph implies a Chrome change is not at fault.  Assigning to current GFX guard for investigation, though I would wait until the cause of crbug.com/768400 is determined.