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

Issue 834100 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

No build number is attached to a data point after new analysis pipeline is in place

Project Member Reported by st...@chromium.org, Apr 17 2018

Issue description

Project Member

Comment 1 by bugdroid1@chromium.org, Apr 18 2018

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

commit a0183c99d741abef00acb83acccb3bb3189d63d9
Author: Shuotao Gao <stgao@chromium.org>
Date: Wed Apr 18 00:09:44 2018

[Findit] FlakeAnalyzer - Work around no build number for data points.

In the new flake analysis, all data points have no build number attached to it.
But it is impossible to retrieve a data point for the "suspected" build number.

Bug: 834100

Change-Id: I4ab88d656bf3a02af94e46211716dc277a07d313
Reviewed-on: https://chromium-review.googlesource.com/1016016
Reviewed-by: Chan Li <chanli@chromium.org>
Commit-Queue: Shuotao Gao <stgao@chromium.org>

[modify] https://crrev.com/a0183c99d741abef00acb83acccb3bb3189d63d9/appengine/findit/handlers/flake/check_flake.py

Comment 2 by st...@chromium.org, Jun 7 2018

Jeff: is this still needed? Please confirm, and assign it back to me so that we could clean up the code in the handler.

Comment 3 by st...@chromium.org, Jun 7 2018

Owner: lijeffrey@chromium.org
Owner: st...@chromium.org
data points should have build_number too for display purposes (even now though they're no longer used for display). This bug may be obsolete, as we don't rely on build number anymore.

Sign in to add a comment