Home
last modified time | relevance | path

Searched +full:docker +full:- +full:test +full:- +full:clang (Results 1 – 4 of 4) sorted by relevance

/qemu/
H A D.patchew.yml1 ---
37 Test '{{ test }}' timeout, log:
57 Tester {{ tester }} out of space when running {{ test }}
84 {% if test == "checkpatch" %}
91 {% elif test == "docker-mingw@fedora" or test == "docker-quick@centos8" or test == "asan" %}
94 This series failed the {{ test }} build test. Please find the testing commands and
95 their output below. If you have Docker installed, you can probably reproduce it
98 … {% lines_between logtext start="^=== TEST SCRIPT BEGIN ===$" stop="^=== TEST SCRIPT END ===$" %}
101 {% elif test == "s390x" or test == "FreeBSD" or test == "ppcle" or test == "ppcbe" %}
104 This series failed build test on {{test}} host. Please find the details below.
[all …]
H A Dconfigure14 source_path=$(cd "$(dirname -- "$0")"; pwd)
16 if test "$PWD" -ef "$source_path"
20 MARKER=build/auto-created-by-configure
22 if test -e build
24 if test -f $MARKER
26 rm -rf build
36 echo "your source directory, or try doing an out-of-tree build."
41 # This file is auto-generated by configure to support in-source tree
46 @$(MAKE) -C build -f Makefile $(MAKECMDGOALS)
47 @if test "$(MAKECMDGOALS)" = "distclean" && \
[all …]
/qemu/scripts/coverity-scan/
H A Dcoverity-scan.docker1 # syntax=docker/dockerfile:1.0.0-experimental
3 # Docker setup for running the "Coverity Scan" tools over the source
11 # We don't build on top of the fedora.docker file because we don't
16 # run-coverity-scan script.
20 RUN dnf install -y nosync && \
21 echo -e '#!/bin/sh\n\
22 if test -d /usr/lib64\n\
30 nosync dnf update -y && \
31 nosync dnf install -y \
32 SDL2-devel \
[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
12 Most (but not all) tests are also integrated as an automated test into
16 [./pyvenv/bin/]meson test --suite qemu:softfloat
20 An automated test is written with one of the test frameworks using its
21 generic test functions/classes. The test framework can run the tests and
24 An automated test has essentially three parts:
26 1. The test initialization of the parameters, where the expected parameters,
31 matches the expected result, the test has been successful; otherwise, it has
34 The rest of this document will cover the details for specific test
[all …]