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

Issue 659351 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 677918
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Factory: Execution with PAR may be a problem for partners debugging or testing.

Project Member Reported by hungte@chromium.org, Oct 25 2016

Issue description

As found in crosbug.com/p/58919#c28 , when we provide CL references, partner may try to grab the diff and apply on DUT directly, which would make factory.par out-of-sync and being a problem that is hard to figure out which steps were executed by which version.

We may need to think again about when and how to use factory.par, or maybe something like "generate par on-the-fly".
 
Mergedinto: 677918
Status: Duplicate (was: Untriaged)
I think this can be merged with chromium:677918.

Sign in to add a comment