New issue
Advanced search Search tips

Issue 622104 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----

Blocking:
issue 622093



Sign in to add a comment

timed out swarming task are not marked failed on swarmbucket

Project Member Reported by no...@chromium.org, Jun 21 2016

Issue description

Task https://chromium-swarm.appspot.com/user/task/2f7e0c38fd997a10 timed out but build https://cr-buildbucket.appspot.com/_ah/api/buildbucket/v1/builds/9009485403632683376 was not marked as timed out and got propagated to buildbot and failed there with INVALID_BUILD_DEFINITION error message because "Luci-go Win Tester (Swarming)" builder is not defined in buildbot.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 22 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra.git/+/45e81bfe53c7bfb92cc13606d62bfba134b2bdac

commit 45e81bfe53c7bfb92cc13606d62bfba134b2bdac
Author: nodir <nodir@google.com>
Date: Wed Jun 22 12:48:55 2016

swarmbucket: extend lease to include execution timeout

The lease for build cr-buildbucket.appspot.com/b/9009485403632683376
for task
chromium-swarm.appspot.com/user/task/2f7e0c38fd997a10
expired before swarming task completed because lease expiration time
was less than (expiration + execution_timeout). Fix that

R=vadimsh@chromium.org
BUG= 622104 

Review-Url: https://codereview.chromium.org/2090453002

[modify] https://crrev.com/45e81bfe53c7bfb92cc13606d62bfba134b2bdac/appengine/cr-buildbucket/swarming/swarming.py

Comment 3 by no...@chromium.org, Jun 22 2016

Status: Fixed (was: Started)

Sign in to add a comment