Auto commit by PR queue bot

Auto commit by PR queue bot

fix typo error of ovs-networking.png

Auto commit by PR queue bot

fix the dead link of docker.md

Auto commit by PR queue bot

Move pkg/client/unversioned/cache to pkg/client/cache; it is version-…

Auto commit by PR queue bot

pkg/client/unversioned/cache -> pkg/client/cache
pkg/client/unversioned/record -> pkg/client/record

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

fix the dead link &typo error of docker.md

Race condition and test fixes

Also enable grace stop for service files.

Auto commit by PR queue bot

Our WaitGroup.Add() call might happen after some WaitGroup.Done() calls done
by the controller, so make sure that doesn't happen by doing the Add() calls
before letting the controller run.

--- FAIL: TestUpdate (2.00s)
panic: sync: WaitGroup is reused before previous Wait has returned [recovered]
        panic: sync: WaitGroup is reused before previous Wait has returned

Auto commit by PR queue bot

Auto commit by PR queue bot

Move util.StringSet into its own package

Revert "Turning on pod autoscaler on GCE."

Banish service up and down e2e test in parallel to flaky

A lot of packages use StringSet, but they don't use anything else from
the util package. Moving StringSet into another package will shrink
their dependency trees significantly.

The error messages were inconsistent with what was actually being tested in
regards to timestamps being equal or not.

The Shutdown() call returned immediately, without waiting for all event
distributions to be completed. Even worse, it would close all the watcher
result channels before all the info was sent to them.

Properly wait for all distributor goroutines - currently only one - to be
finished.

This fixes the flaky test TestBroadcasterDropIfChannelFull. Bonus cleanup on
said test too.

Since $id_field already starts with a period, .$id_field would result in the
following in Go 1.5:

error: error parsing template {{range.items}}{{..metadata.name}}:{{end}}, template: output:1: unexpected . after term "."

Apparently, Go 1.4 allowed this. Unnecessary anyway.

Depending on your system, the error might be "Servname not supported for
ai_socktype" instead of "unknown port". Accept both.

For example:
http://www.ducea.com/2006/09/11/error-servname-not-supported-for-ai_socktype/

The error that Go 1.5 returns is different compared to 1.4. Support both.