Searched +full:functional +full:- +full:system +full:- +full:flaky (Results 1 – 3 of 3) sorted by relevance
2 - local: '/.gitlab-ci.d/buildtest-template.yml'4 build-system-alpine:6 - .native_build_job_template7 - .native_build_artifact_template9 - job: amd64-alpine-container12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu13 MAKE_CHECK_ARGS: check-build14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog16 check-system-alpine:19 - job: build-system-alpine[all …]
1 # SPDX-License-Identifier: GPL-2.0-or-later3 # Decorators useful in functional tests31 host operating system does match one of the prohibited38 return skipIf(platform.system() in args,56 Decorator to skip execution of flaky tests, unless59 failure behaviour, so it can be tracked & re-evaluated67 @skipFlakyTest("https://gitlab.com/qemu-project/qemu/-/issues/NNN")71 bug_url = "FIXME: reproduce flaky test and file bug report or remove"90 data storage (over around 500MB-1GB mark) on the host,
7 everything from unit testing and exercising specific sub-systems all8 the way to full blown functional tests. To get an overview of the9 tests you can run ``make check-help`` from either the source or build13 the meson build system so can be run directly from the build tree,16 [./pyvenv/bin/]meson test --suite qemu:softfloat38 -------------------------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 are76 1. Create a new source file. For example, ``tests/unit/foo-test.c``.[all …]