New issue
Advanced search Search tips

Issue 782307 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Milo: weird "416 [Running for: 0]" in Current builds

Project Member Reported by tandrii@chromium.org, Nov 7 2017

Issue description

Comment 1 by no...@chromium.org, Nov 7 2017

Owner: no...@chromium.org
Status: Started (was: Available)
for 0 means runs for 0 seconds, but this is incorrect
Project Member

Comment 3 by bugdroid1@chromium.org, Nov 7 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/luci/luci-go.git/+/8059300fb3fae400a38a19e0de24891fd0c31e0d

commit 8059300fb3fae400a38a19e0de24891fd0c31e0d
Author: Nodir Turakulov <nodir@google.com>
Date: Tue Nov 07 23:47:28 2017

[milo] use current time when computing duration

if end time of an interval is not available, use current time

R=tandrii@chromium.org, iannucci@chromium.org
Bug:  782307 
Change-Id: I97eeb78e5621d203ec9753f06d14a904848a7a50
Reviewed-on: https://chromium-review.googlesource.com/757165
Commit-Queue: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Ryan Tseng <hinoka@chromium.org>

[modify] https://crrev.com/8059300fb3fae400a38a19e0de24891fd0c31e0d/milo/buildsource/buildbucket/builder.go

Comment 4 by no...@chromium.org, Nov 11 2017

Status: Fixed (was: Started)

Sign in to add a comment