New issue
Advanced search Search tips

Issue 667570 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Have cluster telemetry build from last known working build of chromium.

Project Member Reported by dproy@chromium.org, Nov 22 2016

Issue description

Over the last week, my cluster telemetry run failed four times because of a broken chromium bulid. It looks like chromium bulid has been breaking with alarming frequency recently (or I've just started to notice.) Is there a way to run cluster telemetry from a last known working build of chromium? 

I'm not sure if there is a easy way to get the last working revision of chromium, but if this can be implemented that would be tremendously helpful. These runs take a long time to run, and it's a major productivity drop to come back in the morning and see the run failed because of a unrelated compile error.

Example build error: https://chromium-swarm.appspot.com/task?id=3293eb3f065a1f10&refresh=10&show_raw=1
 

Comment 1 by rmis...@google.com, Nov 22 2016

Status: WontFix (was: Untriaged)
There is a deliberate trade-off choice that has been made here.
In the past it used to use LKGR but then patches from users did not apply because they expected ToT. Also the LKGR sometimes lagged behind for several days.
To make it easier for users we use ToT and because of that we could occasionally have compilation failures when the tree is broken.

I have seen compilation failures be pretty rare though. I was looking through your runs and only noticed one failure due to a chromium compilation problem: https://chromium-swarm.appspot.com/task?id=3293eb3f065a1f10&refresh=10&show_raw=1

Comment 2 by dproy@chromium.org, Nov 22 2016

Ah I see. Now that I'm looking back at my logs you're right - only one of my scheduled builds had compile issues. Perhaps I got frustrated looking at the chromium waterfall - the tree closed 10 times yesterday and I thought that was causing my runs to fails. Thanks for the explanation.

Sign in to add a comment