Searched +full:functional +full:- +full:system +full:- +full:flaky (Results 1 – 4 of 4) sorted by relevance
| /openbmc/qemu/tests/functional/qemu_test/ |
| H A D | decorators.py | 1 # SPDX-License-Identifier: GPL-2.0-or-later
3 # Decorators useful in functional tests
32 host operating system does match one of the prohibited
39 return skipIf(platform.system() in args,
57 Decorator to skip execution of flaky tests, unless
60 failure behaviour, so it can be tracked & re-evaluated
68 @skipFlakyTest("https://gitlab.com/qemu-project/qemu/-/issues/NNN")
72 bug_url = "FIXME: reproduce flaky test and file bug report or remove"
91 data storage (over around 500MB-1GB mark) on the host,
137 Decorator to skip execution of a test if the system's
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 2 - local: '/.gitlab-ci.d/buildtest-template.yml'
4 build-system-alpine:
6 - .native_build_job_template
7 - .native_build_artifact_template
9 - job: amd64-alpine-container
12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu
13 MAKE_CHECK_ARGS: check-build
14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog
16 check-system-alpine:
19 - job: build-system-alpine
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | main.rst | 7 everything from unit testing and exercising specific sub-systems all
8 the way to full blown functional tests. To get an overview of the
9 tests you can run ``make check-help`` from either the source or build
13 the meson build system so can be run directly from the build tree,
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``.
[all …]
|
| /openbmc/docs/ |
| H A D | community-membership.md | 8 …------------------- | ------------------------------------------------------ | -------------------…
11 … | [OWNERS] entry within the meta-\* subfolder for the …
27 Role-specific expectations, responsibilities, and requirements are enumerated
34 Gerrit, and pre-submit tests are automatically run for their reviews. Members
41 - Have made multiple contributions to the project or community. Contribution may
43 - Authoring or reviewing code reviews on Gerrit
44 - Filing or commenting on issues on GitHub
45 - Contributing to design review, subproject, or community discussions (e.g.
47 - Subscribed to the [mailing list]
48 - Have read the [contributor guide]
[all …]
|