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