![]() Some tests were testing non-existing plugins, but therefore triggered the retry-loop, which times out after 15-30 seconds. Add some options to allow overriding this timeout during tests. Before: go test -v -run '^(TestGet|TestNewClientWithTimeout)$' === RUN TestGet === RUN TestGet/success === RUN TestGet/not_implemented === RUN TestGet/not_exists WARN[0000] Unable to locate plugin: vegetable, retrying in 1s WARN[0001] Unable to locate plugin: vegetable, retrying in 2s WARN[0003] Unable to locate plugin: vegetable, retrying in 4s WARN[0007] Unable to locate plugin: vegetable, retrying in 8s --- PASS: TestGet (15.02s) --- PASS: TestGet/success (0.00s) --- PASS: TestGet/not_implemented (0.00s) --- PASS: TestGet/not_exists (15.02s) === RUN TestNewClientWithTimeout client_test.go:166: started remote plugin server listening on: http://127.0.0.1:36275 WARN[0015] Unable to connect to plugin: 127.0.0.1:36275/Test.Echo: Post "http://127.0.0.1:36275/Test.Echo": context deadline exceeded (Client.Timeout exceeded while awaiting headers), retrying in 1s WARN[0017] Unable to connect to plugin: 127.0.0.1:36275/Test.Echo: Post "http://127.0.0.1:36275/Test.Echo": context deadline exceeded (Client.Timeout exceeded while awaiting headers), retrying in 2s WARN[0019] Unable to connect to plugin: 127.0.0.1:36275/Test.Echo: Post "http://127.0.0.1:36275/Test.Echo": net/http: request canceled (Client.Timeout exceeded while awaiting headers), retrying in 4s WARN[0024] Unable to connect to plugin: 127.0.0.1:36275/Test.Echo: Post "http://127.0.0.1:36275/Test.Echo": net/http: request canceled (Client.Timeout exceeded while awaiting headers), retrying in 8s --- PASS: TestNewClientWithTimeout (17.64s) PASS ok github.com/docker/docker/pkg/plugins 32.664s After: go test -v -run '^(TestGet|TestNewClientWithTimeout)$' === RUN TestGet === RUN TestGet/success === RUN TestGet/not_implemented === RUN TestGet/not_exists WARN[0000] Unable to locate plugin: this-plugin-does-not-exist, retrying in 1s --- PASS: TestGet (1.00s) --- PASS: TestGet/success (0.00s) --- PASS: TestGet/not_implemented (0.00s) --- PASS: TestGet/not_exists (1.00s) === RUN TestNewClientWithTimeout client_test.go:167: started remote plugin server listening on: http://127.0.0.1:45973 --- PASS: TestNewClientWithTimeout (0.04s) PASS ok github.com/docker/docker/pkg/plugins 1.050s Signed-off-by: Sebastiaan van Stijn <github@gone.nl> |
||
---|---|---|
.. | ||
aaparser | ||
archive | ||
authorization | ||
broadcaster | ||
capabilities | ||
chrootarchive | ||
containerfs | ||
directory | ||
dmesg | ||
fileutils | ||
homedir | ||
idtools | ||
ioutils | ||
jsonmessage | ||
longpath | ||
loopback | ||
meminfo | ||
namesgenerator | ||
parsers | ||
pidfile | ||
platform | ||
platforms | ||
plugingetter | ||
plugins | ||
pools | ||
process | ||
progress | ||
reexec | ||
rootless | ||
stack | ||
stdcopy | ||
streamformatter | ||
stringid | ||
sysinfo | ||
system | ||
tailfile | ||
tarsum | ||
useragent | ||
README.md |
pkg/ is a collection of utility packages used by the Moby project without being specific to its internals.
Utility packages are kept separate from the moby core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Moby organization, to facilitate re-use by other projects. However that is not the priority.
The directory pkg
is named after the same directory in the camlistore project. Since Brad is a core
Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!
Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!