Use gcloud builds, and :latest-$USER

[fejta]

The UX for gcloud changed

[chrislovecnm]

/lgtm
/approve

[chrislovecnm]

@fejta well I tried to approve 🙄

[chrislovecnm]

@fejta WTH is

Error from server: context canceled

That is what e2e failed on. I have seen the error multiple times

[fejta]

/retest
it is what @smukherj1 has been trying to resolve. No clue what it means...

[fejta]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrislovecnm, fejta

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fejta]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[smukherj1]

Fro the quota logs before attempting the service delete, we see the address usage isn't even close to the limit. So IP address quota doesn't seem to be the issue
Log link: https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/bazelbuild_rules_k8s/217/pull-rules-k8s-e2e/384

IP Quota before delete:

• limit: 8.0
  metric: STATIC_ADDRESSES
  usage: 0.0
  --
• limit: 16.0
  metric: IN_USE_ADDRESSES
  usage: 2.0
  --
• limit: 5.0
  metric: GLOBAL_INTERNAL_ADDRESSES
  usage: 0.0

[smukherj1]

/retest

[fejta]

well I guess that answers that..

[fejta]

Searching for "context canceled" kubernetes seems to suggest this has something to do with flakes pulling images

[nlopezgi]

/retest

[chrislovecnm]

/test pull-rules-k8s-e2e

[chrislovecnm]

@fejta the command to do a single test is not working as well

/retest

[smukherj1]

/retest

[smukherj1]

Last failure was a unit test flake
Test output for //k8s:resolver_test: Traceback (most recent call last): File "/root/.cache/bazel/_bazel_prow/0996f4cdf646bf91686374917a22c2ea/sandbox/processwrapper-sandbox/2/execroot/io_bazel_rules_k8s/bazel-out/k8-fastbuild/bin/k8s/resolver_test.runfiles/io_bazel_rules_k8s/k8s/resolver_test.py", line 20, in <module> import unittest File "/usr/lib/python2.7/unittest/__init__.py", line 64, in <module> from .main import TestProgram, main File "/usr/lib/python2.7/unittest/main.py", line 7, in <module> from . import loader, runner ValueError: bad marshal data (tuple size out of range)

[chrislovecnm]

Seen this flake before as well

Error from server: grpc: the client connection is closing

• echo FAILED, cleaning up...
  FAILED, cleaning up..

/retest

[chrislovecnm]

The last test seems to be our archilles heel. Should we remove the last test? What value is it??

[fejta]

/retest

[fejta]

I'm cursed!

[smukherj1]

@fejta Worry not. Your savior has arrived with #219. Approve it and thine curse shall begone

[chrislovecnm]

/lgtm