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

Issue 773134 link

Starred by 1 user
Status: WontFix
Owner:
dgarr...@chromium.org
Closed: Oct 2017
Cc:
█ nxia@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

CQ Master had Git Conflicts pushing to manifest-versions.

Project Member Reported by dgarr...@chromium.org, Oct 9 2017 
This CQ master:

https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16527

Had git conflict errors pushing to manifest-versions:

https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fmaster-paladin%2F16527%2F%2B%2Frecipes%2Fsteps%2FCommitQueueSync%2F0%2Fstdout

This is REALLY not supposed to happen. Only a single builder should be writing to that location.

Looking deeper.

Comment 1 by dgarr...@chromium.org, Oct 10 2017

Cc: nxia@chromium.org
The failure was trying to create a manifest for "10016.0.0-rc2".

The previous build was "10016.0.0-rc1", the following was auccessful with "10016.0.0-rc2"

All other CLs in manifest versions between the two successful paladin masters were release builds, except for:

commit 7df9ba19d4ea2f4938eabbd351e228474deb5f04
Author: chrome-bot <chrome-bot@chromium.org>
Date:   Mon Oct 9 04:02:04 2017 -0700

    Automatic: Start master-nyc-android-pfq master 10016.0.0-rc1
    CrOS-Build-Id: 1926804


All of these changes look normal. There shouldn't have been any conficts with anything actually submitted.

Comment 2 by dgarr...@chromium.org, Oct 10 2017

Owner: dgarr...@chromium.org
Status: WontFix (was: Untriaged)
I'm thinking this was GoB flake. As long as it's an isolated incident, I don't think it's worth much more investigation.

Comment 3 by nxia@chromium.org, Oct 10 2017 

commit a683648f5f0e8f7a35fbff1f7006260270c12579
Author: chrome-bot <chrome-bot@chromium.org>
Date:   Mon Oct 9 05:23:25 2017 -0700

    Automatic checkin: status=fail build_version 10016.0.0 for relm-release

commit 3536ca6157705ec23f339bd40febbe47d66eb0f0
Author: chrome-bot <chrome-bot@chromium.org>
Date:   Mon Oct 9 05:23:04 2017 -0700

    Automatic checkin: status=fail build_version 10016.0.0 for kevin-release

commit 7287803bd27cb027e4a5fae0e2f5265b23fe403b
Author: chrome-bot <chrome-bot@chromium.org>
Date:   Mon Oct 9 05:22:40 2017 -0700

    Automatic checkin: status=fail build_version 10016.0.0 for banon-release


The release builds log long time and commit a lot messages, so CQ master was always not up-to-date
►

Sign in to add a comment