succeeded attributes
| status |
attribute |
duration |
| succeeded |
checks.aarch64-linux.systemd-initrd-swraid
- Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
|
11m 34s |
| succeeded |
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.
|
4m 43s |
| succeeded |
checks.aarch64-linux.systemd-oomd
- The option `systemd.oomd.extraConfig' defined in `/nix/store/fmasn49f010z71q951x7l7cbyld8p4fl-source/nixos/tests/systemd-oomd.nix' has been renamed to `systemd.oomd.settings.OOM'.
|
3m 25s |
| succeeded |
checks.aarch64-linux.systemd-shutdown
- Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
|
3m 26s |
| succeeded |
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"
|
3m 11s |
| succeeded |
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.
|
3m 7s |
| succeeded |
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.
|
12m 22s |
| succeeded |
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.
|
11m 36s |
| succeeded |
checks.x86_64-linux.systemd-oomd
- The option `systemd.oomd.extraConfig' defined in `/nix/store/fmasn49f010z71q951x7l7cbyld8p4fl-source/nixos/tests/systemd-oomd.nix' has been renamed to `systemd.oomd.settings.OOM'.
|
10m 17s |
| succeeded |
checks.x86_64-linux.systemd-shutdown
- Scripted initrd is deprecated and scheduled for removal in 26.11. See the NixOS 26.05 release notes.
|
10m 3s |
| succeeded |
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"
|
9m 48s |
| succeeded |
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.
|
9m 45s |
| succeeded |
checks.aarch64-linux.fsck-systemd-stage-1
|
3m 35s |
| succeeded |
checks.aarch64-linux.simple-vm
|
3m 34s |
| succeeded |
checks.aarch64-linux.switchTest
|
5m 9s |
| succeeded |
checks.aarch64-linux.switchTest-basics
|
2m 35s |
| succeeded |
checks.aarch64-linux.switchTest-units
|
3m 35s |
| succeeded |
checks.aarch64-linux.switchTest-user
|
3m 51s |
| succeeded |
checks.aarch64-linux.systemd
|
5m 15s |
| succeeded |
checks.aarch64-linux.systemd-analyze
|
3m 41s |
| succeeded |
checks.aarch64-linux.systemd-boot-basic
|
16m 22s |
| succeeded |
checks.aarch64-linux.systemd-boot-bootCounting
|
17m 40s |
| succeeded |
checks.aarch64-linux.systemd-boot-bootCountingSpecialisation
|
16m 5s |
| succeeded |
checks.aarch64-linux.systemd-boot-defaultEntry
|
16m 34s |
| succeeded |
checks.aarch64-linux.systemd-boot-defaultEntryWithBootCounting
|
16m 32s |
| succeeded |
checks.aarch64-linux.systemd-boot-edk2-uefi-shell
|
15m 54s |
| succeeded |
checks.aarch64-linux.systemd-boot-extraEntries
|
15m 49s |
| succeeded |
checks.aarch64-linux.systemd-boot-extraFiles
|
15m 47s |
| succeeded |
checks.aarch64-linux.systemd-boot-fallback
|
15m 52s |
| succeeded |
checks.aarch64-linux.systemd-boot-netbootxyz
|
15m 42s |
| succeeded |
checks.aarch64-linux.systemd-boot-secureBoot
|
16m 16s |
| succeeded |
checks.aarch64-linux.systemd-boot-switch-test
|
15m 44s |
| succeeded |
checks.aarch64-linux.systemd-boot-windows
|
15m 39s |
| succeeded |
checks.aarch64-linux.systemd-bpf
|
1m 10s |
| succeeded |
checks.aarch64-linux.systemd-confinement
|
2m 50s |
| succeeded |
checks.aarch64-linux.systemd-coredump
|
46s |
| succeeded |
checks.aarch64-linux.systemd-credentials-tpm2
|
53s |
| succeeded |
checks.aarch64-linux.systemd-cryptenroll
|
1m 18s |
| succeeded |
checks.aarch64-linux.systemd-escaping
|
44s |
| succeeded |
checks.aarch64-linux.systemd-homed
|
1m 21s |
| succeeded |
checks.aarch64-linux.systemd-initrd-btrfs-raid
|
12m 9s |
| succeeded |
checks.aarch64-linux.systemd-initrd-luks-empty-passphrase
|
12m 23s |
| succeeded |
checks.aarch64-linux.systemd-initrd-luks-fido2
|
12m 28s |
| succeeded |
checks.aarch64-linux.systemd-initrd-luks-keyfile
|
11m 34s |
| succeeded |
checks.aarch64-linux.systemd-initrd-luks-password
|
11m 39s |
| succeeded |
checks.aarch64-linux.systemd-initrd-luks-tpm2
|
11m 24s |
| succeeded |
checks.aarch64-linux.systemd-initrd-modprobe
|
55s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-basic
|
51s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-doFlush
|
1m 0s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-dontFlush
|
1m 4s |
| succeeded |
checks.aarch64-linux.systemd-initrd-networkd-ssh
|
1m 7s |
| succeeded |
checks.aarch64-linux.systemd-initrd-shutdown
|
1m 31s |
| succeeded |
checks.aarch64-linux.systemd-initrd-simple
|
1m 19s |
| succeeded |
checks.aarch64-linux.systemd-initrd-vlan
|
1m 46s |
| succeeded |
checks.aarch64-linux.systemd-journal-gateway
|
3m 38s |
| succeeded |
checks.aarch64-linux.systemd-journal-upload
|
4m 3s |
| succeeded |
checks.aarch64-linux.systemd-misc
|
3m 37s |
| succeeded |
checks.aarch64-linux.systemd-networkd
|
3m 50s |
| succeeded |
checks.aarch64-linux.systemd-networkd-bridge
|
4m 15s |
| succeeded |
checks.aarch64-linux.systemd-networkd-dhcpserver
|
3m 37s |
| succeeded |
checks.aarch64-linux.systemd-networkd-dhcpserver-static-leases
|
3m 40s |
| succeeded |
checks.aarch64-linux.systemd-no-tainted
|
45s |
| succeeded |
checks.aarch64-linux.systemd-nspawn
|
3m 32s |
| succeeded |
checks.aarch64-linux.systemd-nspawn-configfile
|
3m 16s |
| succeeded |
checks.aarch64-linux.systemd-package
|
0s |
| succeeded |
checks.aarch64-linux.systemd-portabled
|
1m 10s |
| succeeded |
checks.aarch64-linux.systemd-pstore
|
3m 58s |
| succeeded |
checks.aarch64-linux.systemd-repart-after-initrd
|
11m 30s |
| succeeded |
checks.aarch64-linux.systemd-repart-basic
|
13m 20s |
| succeeded |
checks.aarch64-linux.systemd-repart-create-root
|
13m 23s |
| succeeded |
checks.aarch64-linux.systemd-repart-encrypt-tpm2
|
13m 23s |
| succeeded |
checks.aarch64-linux.systemd-repart-factory-reset
|
13m 47s |
| succeeded |
checks.aarch64-linux.systemd-resolved
|
3m 32s |
| succeeded |
checks.aarch64-linux.systemd-sysupdate
|
3m 28s |
| succeeded |
checks.aarch64-linux.systemd-sysusers-immutable
|
3m 19s |
| succeeded |
checks.aarch64-linux.systemd-sysusers-mutable
|
3m 19s |
| succeeded |
checks.aarch64-linux.systemd-timesyncd
|
3m 5s |
| succeeded |
checks.aarch64-linux.systemd-user-linger
|
5m 14s |
| succeeded |
checks.aarch64-linux.systemd-user-tmpfiles-rules
|
4m 19s |
| succeeded |
checks.x86_64-linux.fsck-systemd-stage-1
|
3m 2s |
| succeeded |
checks.x86_64-linux.hibernate-systemd-stage-1
|
3m 56s |
| succeeded |
checks.x86_64-linux.simple-vm
|
3m 2s |
| succeeded |
checks.x86_64-linux.switchTest
|
4m 6s |
| succeeded |
checks.x86_64-linux.switchTest-basics
|
3m 39s |
| succeeded |
checks.x86_64-linux.switchTest-units
|
2m 51s |
| succeeded |
checks.x86_64-linux.switchTest-user
|
2m 20s |
| succeeded |
checks.x86_64-linux.systemd
|
2m 15s |
| succeeded |
checks.x86_64-linux.systemd-analyze
|
44s |
| succeeded |
checks.x86_64-linux.systemd-binfmt-basic
|
38s |
| succeeded |
checks.x86_64-linux.systemd-binfmt-chroot
|
44s |
| succeeded |
checks.x86_64-linux.systemd-binfmt-ldPreload
|
33s |
| succeeded |
checks.x86_64-linux.systemd-binfmt-preserveArgvZero
|
33s |
| succeeded |
checks.x86_64-linux.systemd-boot-basic
|
5m 17s |
| succeeded |
checks.x86_64-linux.systemd-boot-basicXbootldr
|
13m 21s |
| succeeded |
checks.x86_64-linux.systemd-boot-bootCounting
|
14m 22s |
| succeeded |
checks.x86_64-linux.systemd-boot-bootCountingSpecialisation
|
13m 6s |
| succeeded |
checks.x86_64-linux.systemd-boot-defaultEntry
|
13m 32s |
| succeeded |
checks.x86_64-linux.systemd-boot-defaultEntryWithBootCounting
|
13m 30s |
| succeeded |
checks.x86_64-linux.systemd-boot-edk2-uefi-shell
|
12m 48s |
| succeeded |
checks.x86_64-linux.systemd-boot-entryFilenameXbootldr
|
12m 53s |
| succeeded |
checks.x86_64-linux.systemd-boot-extraEntries
|
12m 46s |
| succeeded |
checks.x86_64-linux.systemd-boot-extraFiles
|
12m 38s |
| succeeded |
checks.x86_64-linux.systemd-boot-fallback
|
12m 51s |
| succeeded |
checks.x86_64-linux.systemd-boot-garbage-collect-entry
|
12m 44s |
| succeeded |
checks.x86_64-linux.systemd-boot-garbageCollectEntryWithBootCounting
|
12m 42s |
| succeeded |
checks.x86_64-linux.systemd-boot-memtest86
|
12m 36s |
| succeeded |
checks.x86_64-linux.systemd-boot-memtestSortKey
|
12m 32s |
| succeeded |
checks.x86_64-linux.systemd-boot-netbootxyz
|
12m 24s |
| succeeded |
checks.x86_64-linux.systemd-boot-secureBoot
|
12m 51s |
| succeeded |
checks.x86_64-linux.systemd-boot-specialisation
|
12m 28s |
| succeeded |
checks.x86_64-linux.systemd-boot-switch-test
|
12m 22s |
| succeeded |
checks.x86_64-linux.systemd-boot-update
|
4m 12s |
| succeeded |
checks.x86_64-linux.systemd-boot-windows
|
12m 10s |
| succeeded |
checks.x86_64-linux.systemd-bpf
|
9m 32s |
| succeeded |
checks.x86_64-linux.systemd-confinement
|
10m 23s |
| succeeded |
checks.x86_64-linux.systemd-coredump
|
7m 38s |
| succeeded |
checks.x86_64-linux.systemd-credentials-tpm2
|
9m 15s |
| succeeded |
checks.x86_64-linux.systemd-cryptenroll
|
9m 25s |
| succeeded |
checks.x86_64-linux.systemd-escaping
|
7m 27s |
| succeeded |
checks.x86_64-linux.systemd-homed
|
12m 42s |
| succeeded |
checks.x86_64-linux.systemd-initrd-btrfs-raid
|
12m 14s |
| succeeded |
checks.x86_64-linux.systemd-initrd-luks-empty-passphrase
|
13m 3s |
| succeeded |
checks.x86_64-linux.systemd-initrd-luks-fido2
|
12m 23s |
| succeeded |
checks.x86_64-linux.systemd-initrd-luks-keyfile
|
12m 10s |
| succeeded |
checks.x86_64-linux.systemd-initrd-luks-password
|
12m 11s |
| succeeded |
checks.x86_64-linux.systemd-initrd-luks-tpm2
|
12m 7s |
| succeeded |
checks.x86_64-linux.systemd-initrd-modprobe
|
8m 39s |
| succeeded |
checks.x86_64-linux.systemd-initrd-networkd-basic
|
7m 54s |
| succeeded |
checks.x86_64-linux.systemd-initrd-networkd-doFlush
|
8m 20s |
| succeeded |
checks.x86_64-linux.systemd-initrd-networkd-dontFlush
|
7m 54s |
| succeeded |
checks.x86_64-linux.systemd-initrd-networkd-openvpn
|
11m 24s |
| succeeded |
checks.x86_64-linux.systemd-initrd-networkd-ssh
|
10m 55s |
| succeeded |
checks.x86_64-linux.systemd-initrd-shutdown
|
11m 10s |
| succeeded |
checks.x86_64-linux.systemd-initrd-simple
|
10m 58s |
| succeeded |
checks.x86_64-linux.systemd-initrd-vlan
|
10m 36s |
| succeeded |
checks.x86_64-linux.systemd-journal-gateway
|
10m 52s |
| succeeded |
checks.x86_64-linux.systemd-journal-upload
|
10m 58s |
| succeeded |
checks.x86_64-linux.systemd-misc
|
10m 42s |
| succeeded |
checks.x86_64-linux.systemd-networkd
|
10m 39s |
| succeeded |
checks.x86_64-linux.systemd-networkd-bridge
|
11m 4s |
| succeeded |
checks.x86_64-linux.systemd-networkd-dhcpserver
|
10m 34s |
| succeeded |
checks.x86_64-linux.systemd-networkd-dhcpserver-static-leases
|
10m 25s |
| succeeded |
checks.x86_64-linux.systemd-no-tainted
|
3m 23s |
| succeeded |
checks.x86_64-linux.systemd-nspawn
|
10m 13s |
| succeeded |
checks.x86_64-linux.systemd-nspawn-configfile
|
9m 57s |
| succeeded |
checks.x86_64-linux.systemd-package
|
0s |
| succeeded |
checks.x86_64-linux.systemd-portabled
|
4m 53s |
| succeeded |
checks.x86_64-linux.systemd-pstore
|
7m 58s |
| succeeded |
checks.x86_64-linux.systemd-repart-after-initrd
|
10m 13s |
| succeeded |
checks.x86_64-linux.systemd-repart-basic
|
10m 10s |
| succeeded |
checks.x86_64-linux.systemd-repart-create-root
|
10m 4s |
| succeeded |
checks.x86_64-linux.systemd-repart-encrypt-tpm2
|
10m 6s |
| succeeded |
checks.x86_64-linux.systemd-repart-factory-reset
|
10m 38s |
| succeeded |
checks.x86_64-linux.systemd-resolved
|
10m 9s |
| succeeded |
checks.x86_64-linux.systemd-sysupdate
|
10m 5s |
| succeeded |
checks.x86_64-linux.systemd-sysusers-immutable
|
9m 53s |
| succeeded |
checks.x86_64-linux.systemd-sysusers-mutable
|
10m 1s |
| succeeded |
checks.x86_64-linux.systemd-timesyncd
|
9m 55s |
| succeeded |
checks.x86_64-linux.systemd-user-linger
|
9m 46s |
| succeeded |
checks.x86_64-linux.systemd-user-tmpfiles-rules
|
10m 44s |