Issue 661337 link

Starred by 1 user

Issue metadata

Status:	WontFix
Owner:	█ nyquist@chromium.org Traveling - Back 2/6
Closed:	Nov 2016
Cc:	dtrainor@chromium.org █ manisca...@chromium.org
EstimatedDays:	----
NextAction:	----
OS:	Android
Pri:	3
Type:	Bug
Archive-Blimp

Blocking:
issue 648672
issue 661360

Add engine identifier for 0.65

Project Member Reported by nyquist@chromium.org, Nov 1 2016

Issue description

OS: Android

For 0.65 the Blimp feedback data should contain an engine identifier and a timestamp as part of the product specific data.

The timestamp helps it so that we can also identify reports across crashes with reassignment to the same engine.

Comment 1 by nyquist@chromium.org, Nov 1 2016

Blockedon: 661360

If this enables us to remove other identifiers from feedback, we should do so. Filed  issue 661360  about this, and blocking this bug on finishing that work as well.

Comment 2 by w...@chromium.org, Nov 11 2016

Cc: dtrainor@chromium.org manisca...@chromium.org
Owner: nyquist@chromium.org
Status: Assigned (was: Untriaged)

Tommy, shouldn't the blocking/blocked-on relationship be the other way around, i.e. we can't trim out other Ids until we have these new ones in-place?