New issue
Advanced search Search tips

Issue 663586 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

CQ experimental builders aren't skipped if NOTRY=true

Project Member Reported by pdr@chromium.org, Nov 9 2016

Issue description

In https://codereview.chromium.org/2482353002 we have the following:
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Despite my ALL CAPS! plea not to try, the CQ still tried ios-simulator-xcode-clang:
https://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xcode-clang/builds/863

I don't think this try run is visible in the regular Rietveld UI, but I think it may still be a bug that we kicked off that trybot run. It's not clear to me whether this patch was held up due to this bot, or landed independent of it finishing.

I'm putting this as P3 since I am not familiar with this trybot, and the patch still landed in ~2 minutes so it wasn't a big deal either way.
 
This is an experimental trybot. It does not block CQ and is only used to test new trybots and estimate their capacity. Andrii, Pawel, do you think we should also not run experimental tryjobs when NOTRY is set to true?
Status: Available (was: Untriaged)
Sergiyb@ analysis is correct. For consistency, I think we indeed shouldn't run experimental if NOTRY is true.
Summary: CQ experimental builders aren't skipped if NOTRY=true (was: ios-simulator-xcode-clang trybot run on CQ revert (notry=true))
Owner: tandrii@chromium.org
Status: Started (was: Available)
https://chrome-internal-review.googlesource.com/305135
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 15 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal.git/+/af7b7ee5d25649c8bdfca7c879ff8287d4e61d4d

commit af7b7ee5d25649c8bdfca7c879ff8287d4e61d4d
Author: Andrii Shyshkalov <tandrii@chromium.org>
Date: Tue Nov 15 13:28:11 2016

Status: Fixed (was: Started)
Should be fixed :)

Sign in to add a comment