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

Issue 715250 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

pre-cq coverage for chromeos-chrome ebuild

Project Member Reported by akes...@chromium.org, Apr 25 2017

Issue description

Forked from email.

The ChromeOS CQ doesn't test changes to the chromeos-chrome ebuild, because it doesn't build chrome from source. In the last month, two CLs have landed to it that needed to be reverted to fix the chrome-pfq:
BuildPackages failed on https://chromium-review.googlesource.com/474237
VMTest failed on https://chromium-review.googlesource.com/463586

Proposal: create a chrome-ebuild-pre-cq config that locally uprevs chrome, and runs through a build/vmtest on some strategically chosen board. This will build chrome from source, so will be slower than a normal pre-cq job, but use a COMMIT-QUEUE.ini such that it only runs on changes to chromeos-chrome-9999.ebuild.
 
Cc: ihf@chromium.org
Owner: dgarr...@chromium.org
Creating such a PreCQ builder SHOULD be easy, but technical debt might get in the way. I'll take a stab at it.
Status: Assigned (was: Untriaged)
This bug is Untriaged and very old.  Because it has an owner, the status will be set to assigned to avoid closing a bug someone is using.  If this bug still needs triage, change it back to Untriaged.
Components: Infra>Client>ChromeOS>CI
Owner: ----
Status: Untriaged (was: Assigned)

Sign in to add a comment