Skip to content
CI tests to run in Beaker
Branch: master
Clone or download
WOnder93 and spbnick serge-testuite: sync with downstream
This patch forward-ports the following commits:

commit 668b5c3f246912cf8f822deb71b6dc6174cea504
Author: Ondrej Mosnacek <omosnace@redhat.com>
Date:   Wed Jun 19 10:16:01 2019 +0200

    Sanity/serge-testsuite: detect xperms support on RHEL-7

    Extended ioctl permission rules are only supported staring with
    3.10.0-875 RHEL-7 kernel. This makes the TC pass on RHEL-7.5.

    Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>

commit 15c6489d277f0377e8279a58b0f80c5cad8afd2a
Author: Ondrej Mosnacek <omosnace@redhat.com>
Date:   Wed Jun 19 10:15:15 2019 +0200

    Sanity/serge-testsuite: fix version check

    Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>

commit 6973613422c0b0e3bb521b94e74d0ad1974397e4
Author: Ondrej Mosnacek <omosnace@redhat.com>
Date:   Tue May 21 14:39:22 2019 +0200

    Sanity/serge-testsuite: Use fixed git commit by default

    This will avoid breakage of testing caused by upstream commits. Old
    functionality can be achieved by running the TC with GIT_BRANCH=master
    param.

    Acked-by: Milos Malik <mmalik@redhat.com>
    Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Latest commit 2a4c697 Jun 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
acpi/acpitable Add test for ACPI table Feb 12, 2019
distribution misc/kernel-fips-mode: move from distribution test bucket to misc Jun 19, 2019
filesystems rhel4 is no longer supported Jun 7, 2019
kdump kdump/include: set crashkernel mem to a range if auto reservation doe… Jun 18, 2019
legacy legacy: Download RPMs from the nightly repository Jun 19, 2019
memory/function/memfd_create add readme for memfd_create test Mar 25, 2019
misc misc/kernel-fips-mode: move from distribution test bucket to misc Jun 19, 2019
networking Enhance case 'ipsec_basic_netns' to avoid random failure Jun 13, 2019
packages serge-testuite: sync with downstream Jun 19, 2019
rt-tests
standards/usex/1.9-29
storage Fix vpd test in case it fails to get test device Jun 11, 2019
stress/stress-ng stress-ng: use rhts-abort to abort May 28, 2019
template/dummy-test Add dummy test Apr 5, 2019
test/misc/machineinfo initial: Add minimal tests for kernel ci May 8, 2018
tracepoints/operational
vm KVM Kernel Self Tests Jun 12, 2019
README.md add back root readme Feb 12, 2019

README.md

Beaker tasks used with skt runner

How to run tests

Here is a list of common prerequisites for all beaker tests. Test-specific dependencies and steps can be found in the README.md within each test's directory.

$ sudo wget -O /etc/yum.repos.d/beaker-client.repo https://beaker-project.org/yum/beaker-client-Fedora.repo
$ sudo wget -O /etc/yum.repos.d/beaker-harness.repo https://beaker-project.org/yum/beaker-harness-Fedora.repo
$ sudo dnf install -y beaker-client beakerlib restraint-rhts

Test onboarding

Currently, all onboarded tests must use the following combinations of result/status fields:

  • SKIP/COMPLETED if the test requirements aren't fulfilled (eg. test is running on incompatible architecture/hardware)
  • PASS/COMPLETED if the test finished successfully
  • WARN/ABORTED in case of infrastructure issues or other errors (eg. the test checks out a git repo and the git server is unavailable)
  • WARN/COMPLETED or FAIL/COMPLETED in case of any test failures, based on how serious they are (left to decide by test authors)

When onboarding a test, please check especially the point about infrastructure issues: a lot of tests simply report a warning if eg. external server can’t be reached and then continue. This kind of situation falls under infrastructure issues and the test must use the WARN/ABORTED combination, otherwise the infrastructure problem is reported to people as a bug in their code!

The order of Beaker tasks in the XML determines if the task is a preparation for the testing or a test. Anything after kpkginstall task is treated as a test and must follow the rules above. Anything except PASS before kpkginstall is treated as infrastructure issue. Machineinfo (to get HW specification) is ran before kpkginstall, so the same logic applies there. PANIC during kpkginstall means the kernel is bad (can't boot).

You can’t perform that action at this time.