New issue
Advanced search Search tips

Issue 839979 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2018
Cc:
akes...@chromium.org
dgarr...@chromium.org
vapier@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

failed to resolve package for vpython/cipd on CrOS pre-cq builders

Project Member Reported by ayatane@chromium.org, May 4 2018 
vpython fails to run in the pre-cq:

chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129338-07:00 9091 0 annotate.go:242] original error: request to the backend failed after multiple attempts
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129412-07:00 9091 0 annotate.go:242] 
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129431-07:00 9091 0 annotate.go:242] goroutine 1:
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129451-07:00 9091 0 annotate.go:242] #0 go.chromium.org/luci/cipd/client/cipd/client.go:120 - cipd.init()
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129465-07:00 9091 0 annotate.go:242]   tag["this error is temporary"]: true
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129482-07:00 9091 0 annotate.go:242] 
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129499-07:00 9091 0 annotate.go:242] #1 go.chromium.org/luci/vpython/./<autogenerated>:1 - cipd.init()
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129514-07:00 9091 0 annotate.go:242] #2 ./<autogenerated>:1 - main.init()
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129527-07:00 9091 0 annotate.go:242] #3 runtime/proc.go:186 - runtime.main()
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129541-07:00 9091 0 annotate.go:242]   annotation #0:
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129554-07:00 9091 0 annotate.go:242]     reason: failed to resolve packages
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129572-07:00 9091 0 annotate.go:242]   annotation #1:
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129586-07:00 9091 0 annotate.go:242]     reason: resolving package
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129600-07:00 9091 0 annotate.go:242]   annotation #2:
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129613-07:00 9091 0 annotate.go:242]     reason: failed to resolve package version (line 0)
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129627-07:00 9091 0 annotate.go:242]   annotation #3:
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129662-07:00 9091 0 annotate.go:242]     reason: failed to resolve package "infra/python/wheels/astroid-py2_py3" at version "version:1.6.3"
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129678-07:00 9091 0 annotate.go:242] 
chromite-0.0.2-r3864: [E2018-05-03T13:31:51.129691-07:00 9091 0 annotate.go:242] #4 runtime/asm_amd64.s:2361 - runtime.goexit()

Affected CL
https://chromium-review.googlesource.com/c/chromiumos/chromite/+/985121

Example pre-cq build
http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8947522919588668560

Comment 1 by ayatane@chromium.org, May 4 2018

Cc: akes...@chromium.org
I tried running a local tryjob to see if that sheds some light; I ran into a different problem  crbug.com/839581 

However my gut instinct is that a local tryjob won't be able to reproduce this error.

These tests using vpython do pass on a developer workstation.

Comment 2 by ayatane@chromium.org, May 7 2018 

The problem is we cannot resolve the hostname chrome-infra-packages.appspot.com inside of the ebuild/emerge.

Comment 3 by dgarr...@chromium.org, May 7 2018

Cc: vapier@chromium.org
The ebuild environment is intentionally blocked from doing a bunch of stuff to avoid ebuilds having side effects.

hostname resolution might be part of that.

Comment 4 by ayatane@chromium.org, May 7 2018

Status: WontFix (was: Untriaged)
Okay, this is WAI.  portage sandboxes package tests.  I've got a workaround for now, which is kosher if you squint at it.

Comment 5 by vapier@chromium.org, May 8 2018

Labels: -Restrict-View-Google OS-Chrome
correct, we've explicitly changed ebuilds to run most src_* phases in a network sandbox which means you only have 127.0.0.1 (and no dns access), for the reasons Don cited.  we don't want network flakiness making tests fail/get randomly slow.
►

Sign in to add a comment