Issue 633833 link

Starred by 2 users

Issue metadata

Status:	Archived
Owner:	hungte@chromium.org
Closed:	Aug 2016
Components:	Factory
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	3
Type:	Bug
VerifyIn-54 VerifyIn-56 VerifyIn-57 VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Optimize workflow for factory repositories

Project Member Reported by hungte@chromium.org, Aug 3 2016

Issue description

Similar to  issue 285940 , we are recently seeing lots of HWTest and VMTest failures that factory code was never executed so we'd like to set factory repo to be ignored for these stages.

Comment 1 Deleted

Project Member

Comment 2 by bugdroid1@chromium.org, Aug 3 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/factory/+/ef2b58a1324c64fef9e4dea180808bb7df439c10

commit ef2b58a1324c64fef9e4dea180808bb7df439c10
Author: Hung-Te Lin <hungte@chromium.org>
Date: Wed Aug 03 03:41:20 2016

Ignore failures in HWTest and VMTest in the commit queue.

Right now, factory changes are rejected if the HWTest or VMTest
stages fail. This is unnecessary as factory changes are very unlikely
to break these stages, because the factory code was not executed in
HWTest and VMTest stages. All factory stuff were only built and archived
in ChromeOS build infrastructure.

BUG= chromium:633833 
TEST=make test

Change-Id: I89e0eb43c99a0d20421edf7c88191b287c1cf7b6
Reviewed-on: https://chromium-review.googlesource.com/365437
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[add] https://crrev.com/ef2b58a1324c64fef9e4dea180808bb7df439c10/COMMIT-QUEUE.ini