8000 Dockerfile: use GO_VERSION build-arg for overriding Go version by thaJeztah · Pull Request #39548 · moby/moby · GitHub
[go: up one dir, main page]

Skip to content

Conversation

thaJeztah
Copy link
Member

This allows overriding the version of Go without making modifications in the
source code, which can be useful to test against multiple versions.

For example:

make GO_VERSION=1.13beta1 shell

@thaJeztah
Copy link
Member Author

experimental failures are unrelated; https://jenkins.dockerproject.org/job/Docker-PRs-experimental/46008/console

13:22:49 FAIL: docker_api_swarm_service_test.go:34: DockerSwarmSuite.TestAPIServiceUpdatePort
13:49:37 FAIL: docker_cli_swarm_test.go:1535: DockerSwarmSuite.TestSwarmPublishDuplicatePorts

@thaJeztah
Copy link
Member Author

Janky failure is a flaky docker-py test

16:36:46 _______________________ ExecTest.test_exec_command_demux _______________________
16:36:46 /docker-py/tests/integration/api_exec_test.py:182: in test_exec_command_demux
16:36:46     assert next(exec_log) == (b'hello out\r\n', None)
16:36:46 E   AssertionError: assert ('hello out\r...rr\r\n', None) == ('hello out\r\n', None)
16:36:46 E     At index 0 diff: 'hello out\r\nhello err\r\n' != 'hello out\r\n'

Copy link
Contributor
@kolyshkin kolyshkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

This is really nice to have; is there any place we can document it? Perhaps docs/contributing/set-up-dev-env.md and/or TESTING.md?

@tiborvass
Copy link
Contributor

@cpuguy83 I think we can leave it as a go version for now and if we have the need to override the entire image, add another variable that defaults to golang:${GO_VERSION}-alpine.

@thaJeztah
Copy link
Member Author

Docker Hub made a whoopsie https://jenkins.dockerproject.org/job/Docker-PRs/54931/console

17:30:20 FAIL: docker_cli_swarm_test.go:342: DockerSwarmSuite.TestSwarmContainerEndpointOptions
17:30:20 
17:30:20 Creating a new daemon
17:30:20 [dc255ac69325d] waiting for daemon to start
17:30:20 [dc255ac69325d] waiting for daemon to start
17:30:20 [dc255ac69325d] daemon started
17:30:20 
17:30:20 assertion failed: error is not nil: exit status 125: Unable to find image 'busybox:glibc' locally
17:30:20 /usr/local/cli/docker: Error response from daemon: Get https://registry-1.docker.io/v2/library/busybox/manifests/glibc: received unexpected HTTP status: 500 Internal Server Error.
17:30:20 See '/usr/local/cli/docker run --help'.
17:30:20 
17:30:20 [dc255ac69325d] Stopping daemon
17:30:20 [dc255ac69325d] exiting daemon
17:30:20 [dc255ac69325d] Daemon stopped

@GordonTheTurtle GordonTheTurtle added the dco/no Automatically set by a bot when one of the commits lacks proper signature label Jul 18, 2019
@GordonTheTurtle

This comment has been minimized.

@GordonTheTurtle GordonTheTurtle removed the dco/no Automatically set by a bot when one of the commits lacks proper signature label Jul 18, 2019
@kolyshkin
Copy link
Contributor

Added a doc commit

Copy link
Member Author
@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

docs LGTM

@andrewhsu
Copy link
Contributor

Looks like the known flaky test in the experimental PR check failed:

FAIL: docker_cli_swarm_test.go:1329: DockerSwarmSuite.TestSwarmClusterRotateUnlockKey

Likely because this PR was based on codeline before #39531 was merged.

thaJeztah and others added 2 commits July 18, 2019 17:36
This allows overriding the version of Go without making modifications in the
source code, which can be useful to test against multiple versions.

For example:

    make GO_VERSION=1.13beta1 shell

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
@kolyshkin
Copy link
Contributor

Likely because this PR was based on codeline before #39531 was merged

You're right. Rebased to master; let's see how it goes.

@andrewhsu
Copy link
Contributor

Sorry, didn't mean to imply this needed to be rebased and tests re-run. I think it is good to go because the only failing test was a known flaky test.

Copy link
Contributor
@andrewhsu andrewhsu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah
Copy link
Member Author

all green now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants
0