nixbot

builds
sign in

Kranzes/systemd-nix-nightly build #26 succeeded

branch master · commit 5a89b9457b · · took 12m 24s · eval 12m 5s

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

36 succeeded ⚠ 2
checks.aarch64-linux.systemd-initrd-swraid
  • Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
1m 25s
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.
1m 8s
checks.aarch64-linux.systemd-boot-basic 53s
checks.aarch64-linux.systemd-boot-bootCounting 2m 31s
checks.aarch64-linux.systemd-boot-bootCountingSpecialisation 47s
checks.aarch64-linux.systemd-boot-defaultEntry 1m 28s
checks.aarch64-linux.systemd-boot-defaultEntryWithBootCounting 1m 25s
checks.aarch64-linux.systemd-boot-edk2-uefi-shell 40s
checks.aarch64-linux.systemd-boot-extraEntries 40s
checks.aarch64-linux.systemd-boot-extraFiles 40s
checks.aarch64-linux.systemd-boot-netbootxyz 40s
checks.aarch64-linux.systemd-boot-secureBoot 1m 24s
checks.aarch64-linux.systemd-boot-switch-test 52s
checks.aarch64-linux.systemd-boot-windows 41s
checks.aarch64-linux.systemd-initrd-btrfs-raid 1m 25s
checks.aarch64-linux.systemd-initrd-networkd-ssh 37s
checks.x86_64-linux.systemd-boot-basic 48s
checks.x86_64-linux.systemd-boot-bootCounting 2m 4s
checks.x86_64-linux.systemd-boot-bootCountingSpecialisation 40s
checks.x86_64-linux.systemd-boot-defaultEntry 1m 11s
checks.x86_64-linux.systemd-boot-defaultEntryWithBootCounting 1m 9s
checks.x86_64-linux.systemd-boot-edk2-uefi-shell 33s
checks.x86_64-linux.systemd-boot-extraEntries 31s
checks.x86_64-linux.systemd-boot-extraFiles 31s
checks.x86_64-linux.systemd-boot-garbage-collect-entry 41s
checks.x86_64-linux.systemd-boot-garbageCollectEntryWithBootCounting 39s
checks.x86_64-linux.systemd-boot-memtest86 32s
checks.x86_64-linux.systemd-boot-memtestSortKey 32s
checks.x86_64-linux.systemd-boot-netbootxyz 33s
checks.x86_64-linux.systemd-boot-secureBoot 1m 10s
checks.x86_64-linux.systemd-boot-specialisation 41s
checks.x86_64-linux.systemd-boot-switch-test 45s
checks.x86_64-linux.systemd-boot-update 24s
checks.x86_64-linux.systemd-boot-windows 34s
checks.x86_64-linux.systemd-initrd-btrfs-raid 1m 8s
checks.x86_64-linux.systemd-initrd-networkd-ssh 33s
128 already built ⚠ 10
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/8vm376qg7hzf9m0hmzqxnvklq4jqvgm3-nixpkgs-patched/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-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.x86_64-linux.systemd-oomd
  • The option `systemd.oomd.extraConfig' defined in `/nix/store/0vr3zjd479a3a43nchzr62s8cj4qbn6x-nixpkgs-patched/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.switchTest —
checks.aarch64-linux.switchTest-basics —
checks.aarch64-linux.switchTest-units —
checks.aarch64-linux.switchTest-user —
checks.aarch64-linux.systemd —
checks.aarch64-linux.systemd-analyze —
checks.aarch64-linux.systemd-boot-fallback —
checks.aarch64-linux.systemd-bpf —
checks.aarch64-linux.systemd-confinement —
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-luks-empty-passphrase —
checks.aarch64-linux.systemd-initrd-luks-fido2 —
checks.aarch64-linux.systemd-initrd-luks-keyfile —
checks.aarch64-linux.systemd-initrd-luks-password —
checks.aarch64-linux.systemd-initrd-luks-tpm2 —
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-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-bridge —
checks.aarch64-linux.systemd-networkd-dhcpserver —
checks.aarch64-linux.systemd-networkd-dhcpserver-static-leases —
checks.aarch64-linux.systemd-networkd-vrf —
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-repart-after-initrd —
checks.aarch64-linux.systemd-repart-basic —
checks.aarch64-linux.systemd-repart-create-root —
checks.aarch64-linux.systemd-repart-encrypt-tpm2 —
checks.aarch64-linux.systemd-repart-factory-reset —
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-timesyncd-nscd-dnssec —
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.hibernate-systemd-stage-1 —
checks.x86_64-linux.simple-vm —
checks.x86_64-linux.switchTest —
checks.x86_64-linux.switchTest-basics —
checks.x86_64-linux.switchTest-units —
checks.x86_64-linux.switchTest-user —
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-boot-basicXbootldr —
checks.x86_64-linux.systemd-boot-entryFilenameXbootldr —
checks.x86_64-linux.systemd-boot-fallback —
checks.x86_64-linux.systemd-bpf —
checks.x86_64-linux.systemd-confinement —
checks.x86_64-linux.systemd-coredump —
checks.x86_64-linux.systemd-credentials-tpm2 —
checks.x86_64-linux.systemd-cryptenroll —
checks.x86_64-linux.systemd-escaping —
checks.x86_64-linux.systemd-homed —
checks.x86_64-linux.systemd-initrd-luks-empty-passphrase —
checks.x86_64-linux.systemd-initrd-luks-fido2 —
checks.x86_64-linux.systemd-initrd-luks-keyfile —
checks.x86_64-linux.systemd-initrd-luks-password —
checks.x86_64-linux.systemd-initrd-luks-tpm2 —
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-openvpn —
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-pstore —
checks.x86_64-linux.systemd-repart-after-initrd —
checks.x86_64-linux.systemd-repart-basic —
checks.x86_64-linux.systemd-repart-create-root —
checks.x86_64-linux.systemd-repart-encrypt-tpm2 —
checks.x86_64-linux.systemd-repart-factory-reset —
checks.x86_64-linux.systemd-resolved —
checks.x86_64-linux.systemd-sysupdate —
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-timesyncd-nscd-dnssec —
checks.x86_64-linux.systemd-user-linger —
checks.x86_64-linux.systemd-user-tmpfiles-rules —