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

Issue 691044 link

Starred by 0 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

external .repo/manifest.xml not getting updated properly with weave remotes

Project Member Reported by vapier@chromium.org, Feb 10 2017

Issue description

this CL is failing on the external bots:
  https://chromium-review.googlesource.com/433081
it can't find the weave source repo.

all the internal bots are passing.  the manifest/full.xml and manifest-internal/external_full.xml are in sync.

looking at the build log:
https://build.chromium.org/p/chromiumos/builders/amd64-generic-paladin/builds/28438/

specifically the sync stage:
https://build.chromium.org/p/chromiumos/builders/amd64-generic-paladin/builds/28438/steps/CommitQueueSync/logs/stdio

when it prints the manifest, doesn't list the weave repo!  if i do the same `repo init` command to get an external checkout, the weave repo shows up just fine there.

when i ssh into the bot, indeed .repo/manifest.xml is missing anything weave related.  both the remote and the <project> for it.  when i look at .repo/manifest/full.xml though, everything is in there.

looks like our .repo/manifest.xml generation logic is incorrectly dropping the weave remotes.
 

Comment 1 by vapier@chromium.org, Feb 10 2017

Summary: external .repo/manifest.xml not getting updated properly with weave remotes (was: .repo/manifest.xml not getting updated properly)
as i wrote this bug, i poked the code, and i think i found the problem:
https://chromium-review.googlesource.com/441124
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 11 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/e137bb923b80571e694951d4c1ae774312c2972b

commit e137bb923b80571e694951d4c1ae774312c2972b
Author: Mike Frysinger <vapier@chromium.org>
Date: Sat Feb 11 08:35:22 2017

cbuildbot: whitelist weave remotes for external manifests

BUG= chromium:691044 
TEST=precq passes

Change-Id: If5e89eb4ac7e193a72f7e1e91d1183587d964435
Reviewed-on: https://chromium-review.googlesource.com/441124
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>

[modify] https://crrev.com/e137bb923b80571e694951d4c1ae774312c2972b/cbuildbot/config_dump.json
[modify] https://crrev.com/e137bb923b80571e694951d4c1ae774312c2972b/cbuildbot/chromeos_config.py

Comment 3 by vapier@chromium.org, Feb 11 2017

Owner: vapier@chromium.org
Status: Fixed (was: Unconfirmed)
the libweave CL landed fine now

Comment 4 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 5 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 6 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 7 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Comment 8 by vapier@chromium.org, Jun 21 2018

Status: Fixed (was: Archived)

Sign in to add a comment