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

Issue 829503 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ jinjingl@chromium.org
ayatane@chromium.org
jclinton@chromium.org
mar...@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

PreCQ Launcher mishandling swarming build cancellation.

Project Member Reported by dgarr...@chromium.org, Apr 5 2018 
This CL:
  https://crrev.com/c/991405

Tested in this build:

  http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8950065116701717152

The PreCQ builder was cancelled mid-build by the PreCQ launcher. It ran through the Report stages.

This caused the PreCQ launcher (which had cancelled the build) to think it had failed and to annotate the CL being tested with the failures.

It's difficult to look at the relevant build logs, because of  https://crbug.com/829497 .

Comment 1 by dgarr...@chromium.org, Apr 5 2018

Owner: mar...@chromium.org
What exactly does swarming do to signal to in in-progress build that it's being cancelled?

We need to adjust cbuildbot to record this correctly.

Comment 3 by dgarr...@chromium.org, Apr 5 2018

Cc: jclinton@chromium.org
Thanks!

Comment 4 by dgarr...@chromium.org, Apr 5 2018

Labels: -Pri-3 Swarming Pri-2

Comment 5 by dgarr...@chromium.org, Apr 11 2018

Summary: PreCQ Launcher mishandling swarming build cancellation. (was: cbuidlbot treats swarming build cancellation differently than buildbot cancellation.)
The only remaining work is in the PreCQ Launcher. It shouldn't be annotating CLs with failures if it cancelled the builders in question.

Comment 6 by ayatane@chromium.org, May 9 2018

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI

Comment 7 by nxia@chromium.org, Jun 8 2018

Cc: -nxia@chromium.org
►

Sign in to add a comment