New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 601460 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

ANGLE's dEQP tests timing out occaisionally

Project Member Reported by jmad...@chromium.org, Apr 7 2016

Issue description

I've seen this happen a few times now, wondering if it's related to the low-priority mode implemented a few weeks ago.

Most recent failure: https://build.chromium.org/p/tryserver.chromium.angle/builders/linux_angle_rel_ng/builds/1050

Prior failures:

https://build.chromium.org/p/tryserver.chromium.angle/builders/linux_angle_rel_ng/builds/988
https://build.chromium.org/p/tryserver.chromium.angle/builders/linux_angle_rel_ng/builds/987
https://build.chromium.org/p/tryserver.chromium.angle/builders/win_angle_rel_ng/builds/1058
https://build.chromium.org/p/tryserver.chromium.angle/builders/win_angle_rel_ng/builds/1056

assigning to Corentin since he was working on the low-priority change, maybe Ken can help. I believe this also affects the Chromium CQ with the optional testers.
 
The two latter links for Linux are unrelated because they were on the 24th while the low-priority mode landed on the 28th. The others look like they could be related.

I'm not super familiar with how the low-priority mode is implemented in practice. Ken, do you know who added that?

Comment 2 by kbr@chromium.org, Apr 7 2016

Cc: vadimsh@chromium.org mar...@chromium.org serg...@chromium.org
Labels: -Pri-3 Infra-Swarming Pri-2
Yes, sergiyb@ added the support for it, and it adjusts the Swarming priority of the jobs.

It does look likely that these tasks timed out because Swarming was too heavily loaded at the time.

maruel@: is there a way to tell for sure whether a task expired because the fleet was too heavily loaded?

Especially since there are not that many of these bots and they are pretty much always loaded, I suppose we should undo the lowering of the priority of the dEQP tests.

Comment 3 by aga...@chromium.org, Apr 26 2016

Components: Infra>Platform>Swarming
Labels: -Infra-Swarming
Project Member

Comment 4 by bugdroid1@chromium.org, May 20 2016

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

commit 99c15188deae7f59aa467196b0d1c90a62855cd2
Author: cwallez <cwallez@google.com>
Date: Fri May 20 02:34:07 2016

Reset the swarming priority of the ANGLE dEQP tests

With reduced swarming, the ANGLE dEQP tests time out sometimes. We
noticed it happening for example when many ANGLE tryjobs are sent.

This partially reverts 11bb0a6c64122c7fe3eca9922f620299ac073016

BUG= 598010 
BUG= 601460 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/1996153002
Cr-Commit-Position: refs/heads/master@{#394961}

[modify] https://crrev.com/99c15188deae7f59aa467196b0d1c90a62855cd2/content/test/gpu/generate_buildbot_json.py
[modify] https://crrev.com/99c15188deae7f59aa467196b0d1c90a62855cd2/testing/buildbot/chromium.gpu.fyi.json

Status: Fixed (was: Assigned)

Sign in to add a comment