New issue
Advanced search Search tips

Issue 810458 link

Starred by 1 user
Status: Fixed
Owner:
yunchao...@intel.com
Closed: Feb 2018
Cc:
geoffl...@chromium.org
jmad...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue angleproject:2205



Sign in to add a comment

On Ozone: GLSLTest.VerifyMaxFragmentUniformVectors/ES2_OPENGLES and GLSLTest.VerifyMaxVertexUniformVectors/ES2_OPENGLES timing out

Project Member Reported by danakj@chromium.org, Feb 8 2018 
Bot: https://ci.chromium.org/buildbot/chromium.gpu.fyi/Linux%20Ozone%20%28Intel%29/

The timeouts started on this build https://ci.chromium.org/buildbot/chromium.gpu.fyi/Linux%20Ozone%20%28Intel%29/12370

Which was only a change to media/base/audio_buffer.cc so that doesn't seem likely.

It's failed consistently so it doesn't look like flake, but maybe it is? The previous build had nothing likely.

Is there something I'm missing with angle CLs that this is testing other than what's rolled into Chrome?

Comment 1 by jmad...@chromium.org, Feb 8 2018

Blocking: angleproject:2205
Cc: geoffl...@chromium.org
Owner: yunchao...@intel.com
Status: Assigned (was: Untriaged)
Dana, the GPU FYI bots always bypass DEPS and use ANGLE's HEAD revision. In this case the real ANGLE regression range is determined from parent_got_angle_revision in builds 12370 and 12369: https://chromium.googlesource.com/angle/angle.git/+log/5420cb2a..8e5ba8b . ANGLE CLs don't ever show up in the blamelists unfortunately.

Yunchao can you update the expectations accordingly?

Comment 2 by danakj@chromium.org, Feb 8 2018 

Thanks for the info!

Comment 3 by yunchao...@intel.com, Feb 12 2018

Status: Fixed (was: Assigned)
I suppose that Geoff's patch at https://chromium-review.googlesource.com/c/angle/angle/+/909291 fixed this issue. So I'd like to mark this issue as fixed. Please re-open it if I am wrong.
►

Sign in to add a comment