New issue
Advanced search Search tips

Issue 739520 link

Starred by 4 users
Status: Duplicate
Merged: issue 427384
Owner:
dhadd...@chromium.org
Closed: Sep 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Get autoupdate_CatchBadSignatures back into use

Project Member Reported by dhadd...@chromium.org, Jul 5 2017 
This test was moved to bvt-perbuild a while ago. Some of the tasks

1. Get it running locally
2. Update to use small payload 
3. Update run locally steps 
4. Move back to bvt-inline
Project Member

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

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/d320ac41edffe5ad3d9e7a0cb3ddcadc91156ce8

commit d320ac41edffe5ad3d9e7a0cb3ddcadc91156ce8
Author: David Haddock <dhaddock@chromium.org>
Date: Thu Jul 13 18:44:42 2017

[autotest] Update the run locally steps of autopdate_CatchBadSignatures.

The control file steps were insufficient to get it running locally.

BUG= chromium:739520 
TEST=test_that <DUT IP> autoupdate_CatchBadSignatures

Change-Id: I81c4b1b3c885a5dde3f3d88c3819d46f92b60a30
Reviewed-on: https://chromium-review.googlesource.com/551097
Commit-Ready: David Haddock <dhaddock@chromium.org>
Tested-by: David Haddock <dhaddock@chromium.org>
Reviewed-by: David Haddock <dhaddock@chromium.org>

[modify] https://crrev.com/d320ac41edffe5ad3d9e7a0cb3ddcadc91156ce8/server/site_tests/autoupdate_CatchBadSignatures/control

Comment 2 by dhadd...@chromium.org, Sep 26 2017

Mergedinto: 427384
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment