New issue
Advanced search Search tips

Issue 807118 link

Starred by 1 user
Status: Fixed
Owner:
no...@chromium.org
Closed: Feb 2018
Cc:
no...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Milo build duration in *builder* page is not the same as build duration in *build* page

Project Member Reported by bpastene@chromium.org, Jan 30 2018 
See build #27 in https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.ci/Android%20arm64%20Builder%20%28dbg%29
Its duration is listed as 2 hrs 49 mins.

Click on that build:
https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.ci/Android%20arm64%20Builder%20%28dbg%29/27
And its duration is now 3hr.

Any explanation for the discrepancy?

Comment 1 by hinoka@chromium.org, Jan 30 2018

Components: -Infra>Platform>Milo Infra>Platform>Buildbucket
Buildbucket thinks this started at 13:25
https://apis-explorer.appspot.com/apis-explorer/?base=https://cr-buildbucket.appspot.com/_ah/api#p/buildbucket/v1/buildbucket.get?id=8956030861002232256&_h=1&

But swarming thinks this started at 13:15
https://chromium-swarm.appspot.com/task?id=3b5c9622f6a94c10&refresh=10&show_raw=1&wide_logs=true

Normally these should be the same, but it looks to me like buildbucket should've set the start time to 13:25.

Comment 2 by no...@chromium.org, Jan 31 2018 

correct: buildbucket should have used swarming task's start time, as opposed now(). I will fix that.

another bug here is milo should have used buildbucket's start time, not swarming's time. That is bug 774345
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 1 2018 

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

commit ed978bda586620576fa27c754e9574b9139bfe70
Author: Nodir Turakulov <nodir@google.com>
Date: Thu Feb 01 01:47:44 2018

[buildbucket] use swarming's timestamps

Use swarming tasks's start and completion times instead of now(), when
available.

R=maruel@chromium.org

Bug:  807118 
Change-Id: I63a2065be2adad420d382172226fe991962bdbdd
Reviewed-on: https://chromium-review.googlesource.com/896573
Commit-Queue: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org>

[modify] https://crrev.com/ed978bda586620576fa27c754e9574b9139bfe70/appengine/cr-buildbucket/swarming/swarming.py
[modify] https://crrev.com/ed978bda586620576fa27c754e9574b9139bfe70/appengine/cr-buildbucket/swarming/test/swarming_test.py

Comment 4 by tandrii@chromium.org, Feb 2 2018

Owner: no...@chromium.org
Status: Started (was: Untriaged)

Comment 5 by no...@chromium.org, Feb 3 2018

Status: Fixed (was: Started)

Comment 6 by efoo@chromium.org, Feb 28 2018

Labels: LUCI-Chromium-CQSets LUCI-Blocker-Chromium-CQSets LUCI-KnownIssues-UI
►

Sign in to add a comment