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

Issue 602359 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

No clang=1 asan=0 coverage in CQ and main waterfall for Android

Project Member Reported by primiano@chromium.org, Apr 11 2016

Issue description

It seems that all Android CQ and main waterfall bots build both with clang=1 and asan=1. This means that if a CL impacts only with clang=1 (but not asan=1) it will land but then break developers.

This happened today in crrev.com/1875043003.
Not sure if WAI due to lack of capacity, or completely unexpected.
 
Cc: phajdan@google.com
Labels: -Infra-CommitQueue
Good point. Usually chrome-eng-review evaluates requests like this.
Components: -Build Infra>Client>Android
I've chatted with jbudorick. We don't think there's that much demand from devs for this for us to set up a new waterfall bot, given the amount of effort and resources and time it'll take to set this up.

Feel free to bring this up to others; if this is deemed important we can easily do this.

In the future, hopefully setup costs will be smaller and this will be an easier request to handle.

Comment 4 by stip@chromium.org, Jul 13 2016

I'm going to mark this as wontfix, as it seems like there's not a lot of support going through to make this a priority. We can look into it next quarter if it is still an issue.

Comment 5 by stip@chromium.org, Jul 13 2016

Status: WontFix (was: Untriaged)

Sign in to add a comment