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

Issue 685770 link

Starred by 1 user
Status: WontFix
Owner:
pprabhu@chromium.org
Closed: Jan 2017
Cc:
█ ravisadineni@chromium.org
█ levarum@chromium.org
vapier@chromium.org
hywu@chromium.org
hidehiko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

bad ebuild chump causing CQ trouble.

Project Member Reported by pprabhu@chromium.org, Jan 26 2017 
Not really an infra issue.

Story so far:
A bad ebuild was chumped: https://chromium-review.googlesource.com/#/c/430532/
This caused build_packages failures.

So, it was reverted:
https://chromium-review.googlesource.com/#/c/433318/

This is not safe, because it had already been uprevved:
https://chromium-review.googlesource.com/#/c/433383/

This un-broke the pre-cq.

But the incremental builders are still hosed:
https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-incremental-paladin/builds/11048

Comment 1 by pprabhu@chromium.org, Jan 26 2017

Cc: vapier@chromium.org
What is the correct way to unbreak us here?
One way I can think of is that we should have never reverted the CLs, instead merely dropped the dependency on it from autotest-deps, so that it wouldn't break build_packages anymore.

But that ship has sailed.

Comment 2 by pprabhu@chromium.org, Jan 26 2017

Status: WontFix (was: Assigned)
Meh, the current run has gotten past this stage. I have no idea why the last one failed (both the reverts were in by the time that one started...)

Comment 3 by pprabhu@chromium.org, Jan 26 2017 

Current run: http://shortn/_qYCH8BFByy

Comment 4 by vapier@chromium.org, Jan 27 2017 

dropping the dep wouldn't help as the uprev logic operates on all ebuilds in all overlays

we don't have an easy way today to revert this sort of thing once it's been automatically uprevved
►

Sign in to add a comment