qemu-patch-raspberry4/tests/docker
Daniel P. Berrange 8a2390a4f4 docker: Don't enable networking as a side-effect of DEBUG=1
When trying to debug problems with tests it is natural to set
DEBUG=1 when starting the docker environment. Unfortunately
this has a side-effect of enabling an eth0 network interface
in the container, which changes the operating environment of
the test suite. IOW tests with fail may suddenly start
working again if DEBUG=1 is set, due to changed network setup.

Add a separate NETWORK variable to allow enablement of
networking separately from DEBUG=1. This can be used in two
ways. To enable the default docker network backend

  make docker-test-build@fedora NETWORK=1

while to enable a specific network backend, eg join the network
associated with the container 'wibble':

  make docker-test-build@fedora NETWORK=container:wibble

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <20170713144352.2212-1-berrange@redhat.com>
[Drop the superfluous second $(subst ...). - Fam]
Signed-off-by: Fam Zheng <famz@redhat.com>
2017-07-17 11:34:20 +08:00
..
dockerfiles docker: add mipsel build target 2017-06-21 15:02:43 +01:00
common.rc new: debian docker targets for cross-compiling 2017-02-24 14:18:11 +08:00
docker.py docker: rebuild image if 'extra files' checksum does not match 2017-06-21 15:01:48 +01:00
Makefile.include docker: Don't enable networking as a side-effect of DEBUG=1 2017-07-17 11:34:20 +08:00
run docker: exec $CMD 2016-09-23 11:48:32 +08:00
test-build tests/docker: test-build script 2016-10-17 10:05:48 +08:00
test-clang docker: Build in a clean directory 2016-10-02 09:47:23 +08:00
test-full docker: Build in a clean directory 2016-10-02 09:47:23 +08:00
test-mingw tests/docker: make test-mingw honour TARGET_LIST 2016-10-17 10:05:48 +08:00
test-quick docker: Build in a clean directory 2016-10-02 09:47:23 +08:00
travis docker: Add travis tool 2016-06-01 17:27:35 +08:00
travis.py docker: Add travis tool 2016-06-01 17:27:35 +08:00