| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
We might be rotating because we reached limits, which is perfectly
fine, so don't fail if that happens.
|
|
|
|
|
|
| |
The rootfs only has 64K UIDs available when booting with virtiofs,
whereas the nspawn tests want to use user namespace which require
more than 64K UIDs.
|
|
|
|
|
| |
/tmp may not be large enough to contain disk images
and will result in strange errors when it runs out of space.
|
|
|
|
| |
Having directories in / causes problems for make-root-on-boot images
|
|
|
|
|
|
|
| |
Let's use oneshot services as we don't need long running services
for the tests we're doing. Let's also increase the sleeps a little
as the current values weren't sufficient when running the test locally
on my machine with mkosi.
|
| |
|
|
|
|
|
|
| |
If 3 lock messages get sent when going to sleep
then we can falsely assume we have woken up if we only assume we have at least two
so checking we have more than we did before sleeping addresses that issue.
|
|
|
|
|
|
|
|
| |
Make sure the correct buildroot gets expanded instead of the default
opensuse build root location.
We also remove debug files from the unpackaged files list as they're
handled separately by rpm.
|
|
|
|
| |
Required for TEST-73-LOCALE.
|
|
|
|
| |
Required for TEST-70-TPM2.
|
|
|
|
| |
Required for TEST-13-NSPAWN.
|
|
|
|
|
| |
Some integration tests expect to be able to reboot so switch to using
the new systemd.crash_action=poweroff instead.
|
| |
|
|
|
|
|
| |
Otherwise it will wait forever waiting for an interface to appear.
See https://github.com/systemd/systemd/issues/29388.
|
|
|
|
| |
Breaks TEST-83-BTRFS if enabled.
|
|
|
|
| |
Required for TEST-73-LOCALE.
|
| |
|
|
|
|
|
| |
The build sources are ephemeral anyways, so we can just remove the patches
instead of hiding them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With bind mounts, the directories we bind mount to get recorded as
the meson source and build directories. This means meson will complain
if we later try to run meson install -C /work/build in the virtual
machine or container. If we use symlinks, the directories we symlink to
will be recorded as the meson source and build directories, which means
meson install -C /work/build will work when executed after booting the
VM or container.
I tried to do the same for debian as well but the debian package tooling
changes directory into the build directory and then does meson setup ..
which is completely broken when switching to a symlink.
|
|
|
|
| |
Required for TEST-13-NSPAWN.
|
| |
|
|\
| |
| | |
shared: create inaccessible files with correct security label
|
| | |
|
| |
| |
| |
| |
| | |
Add helper for open_mkdir_at() which accepts xopen flags, e.g. to pass
XO_LABEL to create the target with the correct security context.
|
| |
| |
| |
| |
| | |
Add helper for mknodat(2) which creates the destination with the correct
security label.
|
| |
| |
| |
| |
| |
| |
| | |
Scripts used to detect files that should be in POTFILES.in, like
intltool-update -m used on https://l10n.gnome.org/module/systemd/,
falsely detect this file as containing translations. Avoid this
behavior by putting the file in POTFILES.skip.
|
| |
| |
| |
| | |
@iainlane doesn't work on Ubuntu infrastructure anymore, and `bionic` is still ESM, but not really supported anymore either.
`noble`, which is the latest Ubuntu, probably is better for testing `systemd` in 2024, and pinging `qa-help` on IRC is the current official way to contact the team behind Ubuntu's infrastructure.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Recent lcov started complaining loudly about unknown lines in gperf
files:
...
Found gcov version: 13.2.1
Using intermediate gcov format
Recording 'internal' directories:
...
Finished processing 1634 GCNO files
Apply filtering..
Message summary:
1 error message:
range: 1
28 warning messages:
gcov: 27
usage: 1
geninfo: ERROR: (range) unknown line '33' in /build/src/home/homed-gperf.gperf: there are only 22 lines in the file.
Use 'geninfo --filter range' to remove out-of-range lines.
(use "geninfo --ignore-errors range ..." to bypass this error)
Since we drop the coverage of built files from the final report anyway,
let's do it also when capturing both initial and real coverage to avoid
this error.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we're not debugging tests, there's no point in persisting the journal,
so let's use the volatile journal storage mode in that case to avoid doing
unnecessary work.
We don't disable journal storage alltogether since various tests check
that stuff is written to the journal.
|
| |
| |
| |
| |
| |
| | |
In mkosi CI, we want persistent journals when running interactively
and runtime journals when running in CI, so let's add a credential
that allows us to configure which one to use.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps pkg/debian from `640ff73` to `9a5adf2`.
---
updated-dependencies:
- dependency-name: pkg/debian
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \
| | |
| | | |
Various mkosi fixes
|
| | |
| | |
| | |
| | |
| | | |
This allows journald to create the directory itself with the right
chattr settings on first boot.
|
|/ / |
|
|\ \
| | |
| | | |
mkosi: Introduce particle profile
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Unfortunately the current mkosi partitioning setup is a bit too
avant-garde for the integration tests. Both in that distributions
aren't ready for it yet (some more than others), and that software
which we depend on in the integration tests isn't ready for it yet
(e.g. libselinux does not read its configuration from /usr).
Let's switch back to a more boring partioning setup by default but
keep the fancy stuff around as a mkosi profile. This means that it
can still be used for manually testing stuff by running
"mkosi --profile particle -f qemu".
|
| | |
| | |
| | |
| | |
| | | |
Makes the test more robust as the command line the image is booted
won't influence the test result.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Workaround for #32436.
The test may fail if the journal is vacuumed or rotated during the test is running.
Let's use the newest archive file for safety.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
bpf_core_type_id_kernel() needs libbpf 1.4.0 when building with gcc
rather than clang, so bump the dependency accordingly.
More precisely, the following change is needed:
https://github.com/libbpf/libbpf/commit/b19fdbf1be21a28f88740375a575ebd9dfbea68f
Related to: https://github.com/systemd/systemd/issues/31869
Follow-up for 8aee931e7ae1adb01eeac0e1e4c0aef6ed3969ec
|
|/ /
| |
| |
| |
| |
| | |
In some environments, systemd-machined might not be restarted on
downgrade. For safety, let's add the usual PIDFDs= fallback here
as well.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we request a DS and the resolver offers an unsigned SOA, a new
auxiliary transaction for the DS will be rejected as a loop, and we
might not make any progress toward finding the DS we need. Let's ensure
that we at least always check the parent in this case.
Fixes: 47690634f157 ("resolved: don't request the SOA for every dns label")
|
|/
|
|
| |
Otherwise the filenames will contain variable paths and break reproducibility
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The kernel headers match on __s390__ so the build fails
../src/nsresourced/bpf/userns_restrict/userns-restrict.bpf.c:159:6: error: Must specify a BPF target arch via __TARGET_ARCH_xxx
void BPF_KPROBE(userns_restrict_free_user_ns, struct work_struct *work) {
^
/usr/include/bpf/bpf_tracing.h:817:20: note: expanded from macro 'BPF_KPROBE'
return ____##name(___bpf_kprobe_args(args)); \
^
/usr/include/bpf/bpf_tracing.h:797:41: note: expanded from macro '___bpf_kprobe_args'
^
/usr/include/bpf/bpf_helpers.h:195:29: note: expanded from macro '___bpf_apply'
^
note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/usr/include/bpf/bpf_tracing.h:789:72: note: expanded from macro '___bpf_kprobe_args1'
^
/usr/include/bpf/bpf_tracing.h:563:29: note: expanded from macro 'PT_REGS_PARM1'
^
<scratch space>:125:6: note: expanded from here
GCC error "Must specify a BPF target arch via __TARGET_ARCH_xxx"
|
|\
| |
| | |
Some cleanups prompted during review
|
| | |
|
| | |
|
| |
| |
| |
| | |
futimens(2) defaults to current time if 'times' is NULL.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Required for integration tests to power off on PID 1 crashes. We
deprecate systemd.crash_reboot and related options by removing them
from the documentation but still parsing them.
|