Home
last modified time | relevance | path

Searched +full:docker +full:- +full:quick (Results 1 – 3 of 3) sorted by relevance

/qemu/
H A D.patchew.yml1 ---
91 {% elif test == "docker-mingw@fedora" or test == "docker-quick@centos8" or test == "asan" %}
95 their output below. If you have Docker installed, you can probably reproduce it
115 ---
117 Please send your feedback to patchew-devel@redhat.com
122 requirements: docker
126 time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
127 docker-quick@centos8:
129 requirements: docker,x86_64
133 time make docker-test-quick@centos8 SHOW_ENV=1 J=14 NETWORK=1
[all …]
/qemu/tests/docker/
H A DMakefile.include1 # Makefile for Docker tests
3 .PHONY: docker docker-help docker-test docker-clean docker-image docker-qemu-src
9 HOST_ARCH = $(shell uname -m)
10 USER = $(if $(NOUSER),,$(shell id -un))
11 UID = $(if $(NOUSER),,$(shell id -u))
13 DOCKER_FILES_DIR := $(SRC_PATH)/tests/docker/dockerfiles
15 DOCKER_DEFAULT_REGISTRY := registry.gitlab.com/qemu-project/qemu
19 RUNC ?= $(if $(shell command -v docker), docker, podman)
20 DOCKER_SCRIPT=$(SRC_PATH)/tests/docker/docker.py --engine $(RUNC)
22 CUR_TIME := $(shell date +%Y-%m-%d-%H.%M.%S.$$$$)
[all …]
/qemu/docs/devel/testing/
H A Dmain.rst7 everything from unit testing and exercising specific sub-systems all
9 tests you can run ``make check-help`` from either the source or build
16 [./pyvenv/bin/]meson test --suite qemu:softfloat
38 -------------------------
49 Different sub-types of "make check" tests will be explained below.
55 .. _unit-tests:
68 In QEMU, unit tests can be invoked with ``make check-unit``. They are
76 1. Create a new source file. For example, ``tests/unit/foo-test.c``.
86 is in ``tests/unit/foo-test.c``, it is enough to add an entry like::
90 'foo-test': [],
[all …]