nixbot

builds
sign in

Kranzes/systemd-nix-nightly build #12 failed

branch master · commit b3f9489c44 · · took 34m 2s

eval warnings 6 kinds · 14 occurrences
  • warn system.stateVersion is not set, defaulting to 26.11. Read why this matters on https://nixos.org/… ×2
  • warn Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes. ×4
  • warn The option `systemd.oomd.extraConfig' defined in `/nix/store/…-source/nixos/tests/systemd-oomd.nix' has been renamed to `systemd.oomd.settings.OOM'. ×2
  • warn The following system users have UIDs higher than 1000: ×2
  • warn The user 'alice' has multiple of the options ×2
  • warn The user 'bob' has multiple of the options ×2

20 failed ⚠ 1
checks.aarch64-linux.systemd-initrd-swraid
  • Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
1s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-boot-bootCounting 23m 59s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"

nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-boot-defaultEntry 21m 37s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-boot-defaultEntryWithBootCounting 24m 2s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-boot-netbootxyz 4s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-boot-switch-test 23m 49s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"

nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-initrd-btrfs-raid 7s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-initrd-luks-empty-passphrase 1s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"
checks.aarch64-linux.systemd-initrd-luks-fido2 6s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"
checks.aarch64-linux.systemd-initrd-luks-keyfile 6s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"
checks.aarch64-linux.systemd-initrd-luks-password 1s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"
checks.aarch64-linux.systemd-initrd-luks-tpm2 8s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"
checks.aarch64-linux.systemd-networkd-vrf 19s
vm-test-run-systemd-networkd-vrf: self.test_script() ~~~~~~~~~~~~~~~~^^ File "/nix/store/j90z8dcvcjd2i05kicxx9a79lq0iay4y-nixos-test-driver-1.1/lib/py … 
vm-test-run-systemd-networkd-vrf:
    self.test_script()
    ~~~~~~~~~~~~~~~~^^
  File "/nix/store/j90z8dcvcjd2i05kicxx9a79lq0iay4y-nixos-test-driver-1.1/lib/python3.14/site-packages/test_driver/driver.py", line 395, in test_script
    exec(self.tests, symbols, None)
    ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<string>", line 25, in <module>
  File "<string>", line 7, in compare
IndexError: list index out of range
checks.aarch64-linux.systemd-repart-after-initrd 2s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-repart-basic 2s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"
checks.aarch64-linux.systemd-repart-create-root 2s
nixos-disk-image: tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it fin … 
nixos-disk-image:
tribuchet: build event stream: code: 'Some resource has been exhausted', message: "build output exceeded the replay buffer; retry after it finishes"
checks.aarch64-linux.systemd-repart-encrypt-tpm2 1s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.aarch64-linux.systemd-repart-factory-reset 3s
nixos-disk-image: tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of … 
nixos-disk-image:
tribuchet: submitting build: code: 'The system is not in a state required for the operation's execution', message: "an output path is part of a different in-flight build"
checks.x86_64-linux.systemd-credentials-tpm2 1m 19s
vm-test-run-systemd-credentials-tpm2: !!! File "<string>", line 29, in <module> !!! machine.succeed("test -e /dev/tpmrm0") !!! !!! RequestedAssertionFail … 
vm-test-run-systemd-credentials-tpm2:
!!!   File "<string>", line 29, in <module>
!!!     machine.succeed("test -e /dev/tpmrm0")
!!! 
!!! RequestedAssertionFailed: command `test -e /dev/tpmrm0` failed (exit code 1)
cleanup
kill QemuMachine (pid 45)
machine # qemu-system-x86_64: terminating on signal 15 from pid 39 (/nix/store/b5bpi6zfajzzrwwpgba2q6li3nnya4bs-python3-3.14.7/bin/python3.14)
(finished: cleanup, in 0.16 seconds)
checks.x86_64-linux.systemd-cryptenroll 1m 10s
vm-test-run-systemd-cryptenroll: !!! File "<string>", line 5, in <module> !!! machine.succeed("test -e /dev/tpmrm0") !!! !!! RequestedAssertionFailed: co … 
vm-test-run-systemd-cryptenroll:
!!!   File "<string>", line 5, in <module>
!!!     machine.succeed("test -e /dev/tpmrm0")
!!! 
!!! RequestedAssertionFailed: command `test -e /dev/tpmrm0` failed (exit code 1)
cleanup
kill QemuMachine (pid 45)
machine # qemu-system-x86_64: terminating on signal 15 from pid 39 (/nix/store/b5bpi6zfajzzrwwpgba2q6li3nnya4bs-python3-3.14.7/bin/python3.14)
(finished: cleanup, in 0.09 seconds)
14 cancelled ⚠ 1
checks.x86_64-linux.systemd-initrd-swraid
  • Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
27m 50s
checks.x86_64-linux.systemd-boot-bootCounting 29m 55s
checks.x86_64-linux.systemd-boot-defaultEntryWithBootCounting 29m 48s
checks.x86_64-linux.systemd-boot-edk2-uefi-shell 29m 55s
checks.x86_64-linux.systemd-boot-extraEntries 29m 53s
checks.x86_64-linux.systemd-boot-garbage-collect-entry 29m 48s
checks.x86_64-linux.systemd-boot-garbageCollectEntryWithBootCounting 29m 41s
checks.x86_64-linux.systemd-boot-secureBoot 29m 31s
checks.x86_64-linux.systemd-boot-switch-test 29m 26s
checks.x86_64-linux.systemd-initrd-btrfs-raid 28m 24s
checks.x86_64-linux.systemd-initrd-luks-empty-passphrase 29m 8s
checks.x86_64-linux.systemd-initrd-luks-fido2 29m 12s
checks.x86_64-linux.systemd-initrd-luks-keyfile 29m 6s
checks.x86_64-linux.systemd-initrd-luks-tpm2 28m 9s
33 succeeded ⚠ 1
checks.x86_64-linux.systemd-journal
  • system.stateVersion is not set, defaulting to 26.11. Read why this matters on https://nixos.org/manual/nixos/stable/options.html#opt-system.stateVersion.
 10m 54s
checks.aarch64-linux.systemd-boot-basic 24m 34s
checks.aarch64-linux.systemd-boot-edk2-uefi-shell 24m 26s
checks.aarch64-linux.systemd-boot-extraEntries 24m 26s
checks.aarch64-linux.systemd-boot-extraFiles 24m 30s
checks.aarch64-linux.systemd-boot-fallback 24m 33s
checks.aarch64-linux.systemd-boot-secureBoot 25m 2s
checks.aarch64-linux.systemd-boot-windows 24m 25s
checks.aarch64-linux.systemd-networkd-bridge 1m 5s
checks.x86_64-linux.hibernate-systemd-stage-1 17m 18s
checks.x86_64-linux.systemd-boot-basic 1m 8s
checks.x86_64-linux.systemd-boot-basicXbootldr 2m 20s
checks.x86_64-linux.systemd-boot-defaultEntry 24m 3s
checks.x86_64-linux.systemd-boot-entryFilenameXbootldr 3m 16s
checks.x86_64-linux.systemd-boot-extraFiles 2m 41s
checks.x86_64-linux.systemd-boot-fallback 2m 46s
checks.x86_64-linux.systemd-boot-memtest86 1m 53s
checks.x86_64-linux.systemd-boot-memtestSortKey 22m 48s
checks.x86_64-linux.systemd-boot-netbootxyz 2m 41s
checks.x86_64-linux.systemd-boot-specialisation 21m 50s
checks.x86_64-linux.systemd-boot-update 2m 2s
checks.x86_64-linux.systemd-boot-windows 2m 37s
checks.x86_64-linux.systemd-initrd-luks-password 24m 48s
checks.x86_64-linux.systemd-initrd-networkd-openvpn 6m 53s
checks.x86_64-linux.systemd-pstore 9m 4s
checks.x86_64-linux.systemd-repart-after-initrd 17m 57s
checks.x86_64-linux.systemd-repart-basic 18m 1s
checks.x86_64-linux.systemd-repart-create-root 15m 57s
checks.x86_64-linux.systemd-repart-encrypt-tpm2 18m 1s
checks.x86_64-linux.systemd-repart-factory-reset 20m 25s
checks.x86_64-linux.systemd-resolved 2m 7s
checks.x86_64-linux.systemd-sysupdate 4m 54s
checks.x86_64-linux.systemd-user-tmpfiles-rules 5m 9s
83 already built ⚠ 9
checks.aarch64-linux.systemd-journal
  • system.stateVersion is not set, defaulting to 26.11. Read why this matters on https://nixos.org/manual/nixos/stable/options.html#opt-system.stateVersion.
 —
checks.aarch64-linux.systemd-oomd
  • The option `systemd.oomd.extraConfig' defined in `/nix/store/mfaj27iam74lx445ppslfjnb0nsz7ww8-source/nixos/tests/systemd-oomd.nix' has been renamed to `systemd.oomd.settings.OOM'.
 —
checks.aarch64-linux.systemd-shutdown
  • Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
—
checks.aarch64-linux.systemd-sysusers-password-option-override-ordering
  • The user 'alice' has multiple of the options `initialHashedPassword`, `hashedPassword`, `initialPassword`, `password` & `hashedPasswordFile` set to a non-null value. If multiple of these password options are set at the same time then a specific order of precedence is followed, which can lead to surprising results. The order of precedence differs depending on whether the {option}`users.mutableUsers` option is set. If the option {option}`users.mutableUsers` is `true`, then the order of precedence is as shown below, where values on the left are overridden by values on the right: {option}`initialHashedPassword` -> {option}`initialPassword` -> {option}`hashedPassword` -> {option}`password` -> {option}`hashedPasswordFile` The values of these options are: * users.users."alice".hashedPassword: null * users.users."alice".hashedPasswordFile: null * users.users."alice".password: null * users.users."alice".initialHashedPassword: "$y$j9T$wLgKY231.8j.ciV2MfEXe1$P0k5j3bCwHgnwW0Ive3w4knrgpiA4TzhCYLAnHvDZ51" * users.users."alice".initialPassword: "test"
  • The user 'bob' has multiple of the options `initialHashedPassword`, `hashedPassword`, `initialPassword`, `password` & `hashedPasswordFile` set to a non-null value. If multiple of these password options are set at the same time then a specific order of precedence is followed, which can lead to surprising results. The order of precedence differs depending on whether the {option}`users.mutableUsers` option is set. If the option {option}`users.mutableUsers` is `true`, then the order of precedence is as shown below, where values on the left are overridden by values on the right: {option}`initialHashedPassword` -> {option}`initialPassword` -> {option}`hashedPassword` -> {option}`password` -> {option}`hashedPasswordFile` The values of these options are: * users.users."bob".hashedPassword: null * users.users."bob".hashedPasswordFile: "/nix/store/j5issrx4q7zkwrp2g11w6ymcajqsfhmz-hashed-password" * users.users."bob".password: null * users.users."bob".initialHashedPassword: "$y$j9T$wLgKY231.8j.ciV2MfEXe1$P0k5j3bCwHgnwW0Ive3w4knrgpiA4TzhCYLAnHvDZ51" * users.users."bob".initialPassword: "test"
—
checks.aarch64-linux.systemd-userdbd
  • The following system users have UIDs higher than 1000: nixbld1 nixbld10 nixbld11 nixbld12 nixbld13 nixbld14 nixbld15 nixbld16 nixbld17 nixbld18 nixbld19 nixbld2 nixbld20 nixbld21 nixbld22 nixbld23 nixbld24 nixbld25 nixbld26 nixbld27 nixbld28 nixbld29 nixbld3 nixbld30 nixbld31 nixbld32 nixbld4 nixbld5 nixbld6 nixbld7 nixbld8 nixbld9 These users will be recognized by systemd-userdb as "regular" users, not "system" users. This will affect programs that query regular users, such as systemd-homed, which will not run the first boot user creation flow, as regular users already exist. To fix this issue, please remove or redefine these system users to have UIDs below 1000. For Nix build users, it's possible to adjust the base build user ID using the `ids.uids.nixbld` option, however care must be taken to avoid collisions with UIDs of other services. Alternatively, you may enable the `auto-allocate-uids` experimental feature and option in the Nix configuration to avoid creating these users, however please note that this option is experimental and subject to change. Alternatively, to acknowledge and silence this warning, set `services.userdbd.silenceHighSystemUsers` to true.
—
checks.x86_64-linux.systemd-oomd
  • The option `systemd.oomd.extraConfig' defined in `/nix/store/mfaj27iam74lx445ppslfjnb0nsz7ww8-source/nixos/tests/systemd-oomd.nix' has been renamed to `systemd.oomd.settings.OOM'.
 —
checks.x86_64-linux.systemd-shutdown
  • Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
—
checks.x86_64-linux.systemd-sysusers-password-option-override-ordering
  • The user 'alice' has multiple of the options `initialHashedPassword`, `hashedPassword`, `initialPassword`, `password` & `hashedPasswordFile` set to a non-null value. If multiple of these password options are set at the same time then a specific order of precedence is followed, which can lead to surprising results. The order of precedence differs depending on whether the {option}`users.mutableUsers` option is set. If the option {option}`users.mutableUsers` is `true`, then the order of precedence is as shown below, where values on the left are overridden by values on the right: {option}`initialHashedPassword` -> {option}`initialPassword` -> {option}`hashedPassword` -> {option}`password` -> {option}`hashedPasswordFile` The values of these options are: * users.users."alice".hashedPassword: null * users.users."alice".hashedPasswordFile: null * users.users."alice".password: null * users.users."alice".initialHashedPassword: "$y$j9T$wLgKY231.8j.ciV2MfEXe1$P0k5j3bCwHgnwW0Ive3w4knrgpiA4TzhCYLAnHvDZ51" * users.users."alice".initialPassword: "test"
  • The user 'bob' has multiple of the options `initialHashedPassword`, `hashedPassword`, `initialPassword`, `password` & `hashedPasswordFile` set to a non-null value. If multiple of these password options are set at the same time then a specific order of precedence is followed, which can lead to surprising results. The order of precedence differs depending on whether the {option}`users.mutableUsers` option is set. If the option {option}`users.mutableUsers` is `true`, then the order of precedence is as shown below, where values on the left are overridden by values on the right: {option}`initialHashedPassword` -> {option}`initialPassword` -> {option}`hashedPassword` -> {option}`password` -> {option}`hashedPasswordFile` The values of these options are: * users.users."bob".hashedPassword: null * users.users."bob".hashedPasswordFile: "/nix/store/a2yv02h3ks47driql2g2pcihyfj4rdmv-hashed-password" * users.users."bob".password: null * users.users."bob".initialHashedPassword: "$y$j9T$wLgKY231.8j.ciV2MfEXe1$P0k5j3bCwHgnwW0Ive3w4knrgpiA4TzhCYLAnHvDZ51" * users.users."bob".initialPassword: "test"
—
checks.x86_64-linux.systemd-userdbd
  • The following system users have UIDs higher than 1000: nixbld1 nixbld10 nixbld11 nixbld12 nixbld13 nixbld14 nixbld15 nixbld16 nixbld17 nixbld18 nixbld19 nixbld2 nixbld20 nixbld21 nixbld22 nixbld23 nixbld24 nixbld25 nixbld26 nixbld27 nixbld28 nixbld29 nixbld3 nixbld30 nixbld31 nixbld32 nixbld4 nixbld5 nixbld6 nixbld7 nixbld8 nixbld9 These users will be recognized by systemd-userdb as "regular" users, not "system" users. This will affect programs that query regular users, such as systemd-homed, which will not run the first boot user creation flow, as regular users already exist. To fix this issue, please remove or redefine these system users to have UIDs below 1000. For Nix build users, it's possible to adjust the base build user ID using the `ids.uids.nixbld` option, however care must be taken to avoid collisions with UIDs of other services. Alternatively, you may enable the `auto-allocate-uids` experimental feature and option in the Nix configuration to avoid creating these users, however please note that this option is experimental and subject to change. Alternatively, to acknowledge and silence this warning, set `services.userdbd.silenceHighSystemUsers` to true.
—
checks.aarch64-linux.fsck-systemd-stage-1 —
checks.aarch64-linux.simple-vm —
checks.aarch64-linux.systemd —
checks.aarch64-linux.systemd-analyze —
checks.aarch64-linux.systemd-bpf —
checks.aarch64-linux.systemd-coredump —
checks.aarch64-linux.systemd-credentials-tpm2 —
checks.aarch64-linux.systemd-cryptenroll —
checks.aarch64-linux.systemd-escaping —
checks.aarch64-linux.systemd-homed —
checks.aarch64-linux.systemd-initrd-modprobe —
checks.aarch64-linux.systemd-initrd-networkd-basic —
checks.aarch64-linux.systemd-initrd-networkd-doFlush —
checks.aarch64-linux.systemd-initrd-networkd-dontFlush —
checks.aarch64-linux.systemd-initrd-networkd-ssh —
checks.aarch64-linux.systemd-initrd-shutdown —
checks.aarch64-linux.systemd-initrd-simple —
checks.aarch64-linux.systemd-initrd-vlan —
checks.aarch64-linux.systemd-journal-gateway —
checks.aarch64-linux.systemd-journal-upload —
checks.aarch64-linux.systemd-misc —
checks.aarch64-linux.systemd-networkd —
checks.aarch64-linux.systemd-networkd-dhcpserver —
checks.aarch64-linux.systemd-networkd-dhcpserver-static-leases —
checks.aarch64-linux.systemd-no-tainted —
checks.aarch64-linux.systemd-nspawn —
checks.aarch64-linux.systemd-nspawn-configfile —
checks.aarch64-linux.systemd-package —
checks.aarch64-linux.systemd-portabled —
checks.aarch64-linux.systemd-pstore —
checks.aarch64-linux.systemd-resolved —
checks.aarch64-linux.systemd-sysupdate —
checks.aarch64-linux.systemd-sysusers-immutable —
checks.aarch64-linux.systemd-sysusers-mutable —
checks.aarch64-linux.systemd-timesyncd —
checks.aarch64-linux.systemd-user-linger —
checks.aarch64-linux.systemd-user-tmpfiles-rules —
checks.x86_64-linux.fsck-systemd-stage-1 —
checks.x86_64-linux.simple-vm —
checks.x86_64-linux.systemd —
checks.x86_64-linux.systemd-analyze —
checks.x86_64-linux.systemd-binfmt-basic —
checks.x86_64-linux.systemd-binfmt-chroot —
checks.x86_64-linux.systemd-binfmt-ldPreload —
checks.x86_64-linux.systemd-binfmt-preserveArgvZero —
checks.x86_64-linux.systemd-bpf —
checks.x86_64-linux.systemd-coredump —
checks.x86_64-linux.systemd-escaping —
checks.x86_64-linux.systemd-homed —
checks.x86_64-linux.systemd-initrd-modprobe —
checks.x86_64-linux.systemd-initrd-networkd-basic —
checks.x86_64-linux.systemd-initrd-networkd-doFlush —
checks.x86_64-linux.systemd-initrd-networkd-dontFlush —
checks.x86_64-linux.systemd-initrd-networkd-ssh —
checks.x86_64-linux.systemd-initrd-shutdown —
checks.x86_64-linux.systemd-initrd-simple —
checks.x86_64-linux.systemd-initrd-vlan —
checks.x86_64-linux.systemd-journal-gateway —
checks.x86_64-linux.systemd-journal-upload —
checks.x86_64-linux.systemd-misc —
checks.x86_64-linux.systemd-networkd —
checks.x86_64-linux.systemd-networkd-bridge —
checks.x86_64-linux.systemd-networkd-dhcpserver —
checks.x86_64-linux.systemd-networkd-dhcpserver-static-leases —
checks.x86_64-linux.systemd-networkd-vrf —
checks.x86_64-linux.systemd-no-tainted —
checks.x86_64-linux.systemd-nspawn —
checks.x86_64-linux.systemd-nspawn-configfile —
checks.x86_64-linux.systemd-package —
checks.x86_64-linux.systemd-portabled —
checks.x86_64-linux.systemd-sysusers-immutable —
checks.x86_64-linux.systemd-sysusers-mutable —
checks.x86_64-linux.systemd-timesyncd —
checks.x86_64-linux.systemd-user-linger —