summaryrefslogtreecommitdiffstats
path: root/test/fmf (follow)
Commit message (Collapse)AuthorAgeFilesLines
* fmf: Only move logs if corresponding directory existsDaan De Meyer2025-01-141-2/+2
| | | | Otherwise find fails with an error.
* fmf: Skip TEST-21-DFUZZERDaan De Meyer2025-01-101-0/+4
| | | | | Similar to Github Actions, since we don't build with sanitizers in the packit job, let's skip TEST-21-DFUZZER.
* fmf: Use different heuristic on beefy systemsDaan De Meyer2025-01-101-1/+9
| | | | | | If we save journals in /tmp, we can run a larger number of tests in parallel so let's make use of the larger number of CPUs if the tests run on a beefy machine.
* fmf: Bump inotify limits to avoid systemd-nspawn failuresDaan De Meyer2025-01-101-0/+4
|
* fmf: Use one fewer than number of available CPUs againDaan De Meyer2025-01-091-8/+1
| | | | | | | | | This effectively reverts b8582198ca1e6fe390f7169e623a9130b68a6b36 as I can not get the testing farm bare metal machines working downstream and even if I managed to, without also using the testing farm bare metal machines upstream (for which there is no capacity), the setup would very quickly bitrot anyway so we'll just run the container based tests for now.
* fmf: Log clock sourceDaan De Meyer2025-01-091-0/+2
|
* fmf: Move meson logs and failed test journals to test artifacts dirDaan De Meyer2025-01-091-1/+6
|
* fmf: Force SELinux relabel when running within testing farmDaan De Meyer2025-01-091-0/+3
| | | | | We expect to run as root within testing farm and to have permissions to do selinux relabelling so let's enable it explicitly.
* TEST-06-SELINUX: Add knob to allow checking for AVCsDaan De Meyer2025-01-091-0/+7
| | | | | | When running the integration tests downstream, it's useful to be able to test that a new systemd version doesn't introduce any AVC denials, so let's add a knob to make that possible.
* fmf: Use different heuristic for number of process with many CPUsDaan De Meyer2025-01-091-1/+8
| | | | | | | Downstream we sometimes end up with machines with lots of CPUs which leads to running out of memory when trying to run the tests in VMs. So let's switch to a different heuristic when we have lots of CPUs to avoid running out of memory.
* fmf: Dump CPU and memory informationDaan De Meyer2025-01-081-0/+4
|
* fmf: Only mess with /etc/yum.repos.d when running within testing farmDaan De Meyer2025-01-081-6/+12
| | | | | If running tmt locally to debug the test script, make sure we don't mess with /etc/yum.repos.d.
* fmf: Fix globDaan De Meyer2025-01-081-1/+4
| | | | | | Globs inside quotes aren't expanded and we need the glob to be more specific to avoid matching multiple entries inside the tmt source directory.
* fmf: Fix dist-git exampleDaan De Meyer2025-01-081-3/+0
| | | | | All that's needed is dist-git-source: true so remove the other settings that aren't required.
* fmf: Don't fail if we can't put selinux in permissive modeDaan De Meyer2025-01-081-2/+2
| | | | | The tests might be running unprivileged or in an environment without selinux so let's not fail if we can't put it in permissive mode.
* fmf: Check out target branch in packitDaan De Meyer2025-01-071-1/+1
|
* fmf: Support being used downstream in dist-git testsDaan De Meyer2025-01-061-9/+37
| | | | | | | | | We can use our upstream fmf definitions to run downstream tests in the Fedora systemd dist-git repository (https://src.fedoraproject.org/rpms/systemd). To have access to the dist-git sources when running the tests, we enable dist-git-source: true downstream which makes the sources available in $TMT_SOURCE_DIR so let's make sure we use those sources if they're available.
* fmf: Insist on mkosi sha being availableDaan De Meyer2025-01-061-8/+2
| | | | | | | | Let's assume the workflow file containing the mkosi always being available. Also fix the detection while we're at it by not leaving the systemd directory.
* packit: Move fmf metadata into upstreamDaan De Meyer2025-01-054-0/+111
This moves https://src.fedoraproject.org/tests/systemd into upstream so it's one less moving piece that we need to remember. While we're at it, do various cleanups as well: - Remove non-packit logic - Set NO_BUILD in mkosi.local.conf as it's not picked up from the process environment - Don't set unused environment variables - Remove workdir logic as we run in an ephemeral VM already - Drop --verbose from meson test to reduce noise from passed tests - Use mkosi sandbox and drop duplicated deps from metadata file - Stop running the unit tests as they already run as part of the rpm build and as part of the integration tests. - Various style fixes