The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cd982de8032d8f01aababb80bf9137c148425690

commit cd982de8032d8f01aababb80bf9137c148425690
Author: Greg Thompson <grt@chromium.org>
Date: Fri Mar 02 13:20:20 2018

Mark virtual/gpu-rasterization/images/gif-loop-count.html as flaky.

BUG=818154
TBR=grt@chromium.org

Change-Id: Ifef703601046ece334cf571c32866d1ce0aabab9
Reviewed-on: https://chromium-review.googlesource.com/945993
Commit-Queue: Greg Thompson <grt@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540506}
[modify] https://crrev.com/cd982de8032d8f01aababb80bf9137c148425690/third_party/WebKit/LayoutTests/TestExpectations

This only seems to be failing on the GPU rasterization bot and only in debug ( https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=if-loop-count.html ), and the errors above look like something rasterization-related rather than in the image decoders.  I think someone from the GPU rasterization team needs to look at this rather than me.

Not sure who owns those.  The component is already set correctly, hopefully marking as untriaged means they'll pick it up?

This failed a few times but has been fine since. I suspect a temporary situation due to machine load or similar. It does tend to be flaky on Win bots, requiring repeat to pass, but the only way I can think of to avoid that would be to increase the timeouts in it and make it always slower. That seems like a bad idea.

I'm going to remove it from TestExpectations.

I'll take a look.