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

Issue 764508 link

Starred by 1 user
Status: WontFix
Owner:
shapiroc@chromium.org
Closed: Jan 11
Cc:
█ ppichai@google.com
adurbin@chromium.org
█ pbe...@chromium.org
yueherngl@chromium.org
jclinton@chromium.org
nsanders@chromium.org
shapiroc@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Chase down things that use hardware ID when they should use model

Project Member Reported by sjg@chromium.org, Sep 12 2017 
There are a few places where we do not have support for using the model
name at present:

- feedback reports
- targetting auto-update by component (e.g. particular MMC, DRAM)
- metrics tracking / device actives

For feedback reports, for example, we use a regex on the hardware ID to collate reports for similar devices.

We should investigate the above cases and figure out what to do in a unified-build world.
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 13 2017 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-coral-private/+/412c4ddb17ce563f19fdf0b1b034c3c3d47e8d41

commit 412c4ddb17ce563f19fdf0b1b034c3c3d47e8d41
Author: Simon Glass <sjg@chromium.org>
Date: Wed Sep 13 06:48:28 2017

Comment 2 by nsanders@chromium.org, Sep 13 2017 

I think the issue here is that many of the tools need to identify the hardware device and unibuild "model" doesn't map directly to that. So to explicitly cover this case rather than using regex, we'd need either new identifier (maybe chassis-id) or rework model to map 1:1 with device, rather than keyset.

Comment 3 by adurbin@chromium.org, Sep 13 2017 

I think we should enumerate the details of the data people are needing and go from there. Without the details/data it's hard to speculate on the real needs.

Comment 4 by sjg@chromium.org, Nov 4 2017

Labels: Unibuild

Comment 5 by sjg@chromium.org, Apr 25 2018

Owner: shapiroc@chromium.org
->Charles for triage

Comment 6 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Comment 7 by shapiroc@chromium.org, Jan 11

Status: WontFix (was: Assigned)
►

Sign in to add a comment