nixbot

builds
sign in

nix-community/disko build #172 succeeded

branch gh-readonly-queue/master/pr-1297-ff8702b4de27f72b4c78573dfb89ec74e36abdf1 · commit 4084b6c7bd · · took 2m 16s · eval 1m 21s

eval warnings 5 kinds · 21 occurrences
  • error "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," ×9
  • warn The legacy table is outdated and should not be used. We recommend using the gpt type instead. ×9
  • warn mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash. ×1
  • warn the create output is deprecated and will be removed, please open an issue if you're using it! ×1
  • warn the mount output is deprecated and will be removed, please open an issue if you're using it! ×1

8 succeeded
loading…
51 already built ⚠ 6
checks.aarch64-linux.jsonTypes
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
—
checks.x86_64-linux.jsonTypes
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
—
checks.x86_64-linux.legacy-table
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
—
checks.x86_64-linux.legacy-table-with-whitespace
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
—
checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
 —
checks.x86_64-linux.standalone
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
  • the create output is deprecated and will be removed, please open an issue if you're using it!
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
  • the mount output is deprecated and will be removed, please open an issue if you're using it!
  • The legacy table is outdated and should not be used. We recommend using the gpt type instead. Please note that certain features, such as the test framework, may not function properly with the legacy table type. If you encounter errors similar to: "error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times," this is likely due to the use of the legacy table type. for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
—
checks.aarch64-darwin.checkJqSyntax —
checks.aarch64-darwin.jsonTypes —
checks.aarch64-linux.checkJqSyntax —
checks.x86_64-linux.bcachefs —
checks.x86_64-linux.boot-raid1 —
checks.x86_64-linux.btrfs-only-root-subvolume —
checks.x86_64-linux.btrfs-subvolumes —
checks.x86_64-linux.checkJqSyntax —
checks.x86_64-linux.cli —
checks.x86_64-linux.complex —
checks.x86_64-linux.f2fs —
checks.x86_64-linux.gpt-bios-compat —
checks.x86_64-linux.gpt-name-with-special-chars —
checks.x86_64-linux.gpt-unformatted —
checks.x86_64-linux.hybrid —
checks.x86_64-linux.hybrid-mbr —
checks.x86_64-linux.hybrid-tmpfs-on-root —
checks.x86_64-linux.long-device-name —
checks.x86_64-linux.luks-btrfs-raid —
checks.x86_64-linux.luks-btrfs-subvolumes —
checks.x86_64-linux.luks-fido2 —
checks.x86_64-linux.luks-interactive-login —
checks.x86_64-linux.luks-lvm —
checks.x86_64-linux.luks-on-mdadm —
checks.x86_64-linux.lvm-raid —
checks.x86_64-linux.lvm-sizes-sort —
checks.x86_64-linux.lvm-thin —
checks.x86_64-linux.make-disk-image —
checks.x86_64-linux.make-disk-image-impure —
checks.x86_64-linux.mdadm —
checks.x86_64-linux.mdadm-raid0 —
checks.x86_64-linux.mdadm-raid5-args —
checks.x86_64-linux.module —
checks.x86_64-linux.multi-device-no-deps —
checks.x86_64-linux.negative-size —
checks.x86_64-linux.non-root-zfs —
checks.x86_64-linux.simple-efi —
checks.x86_64-linux.swap —
checks.x86_64-linux.tmpfs —
checks.x86_64-linux.with-lib —
checks.x86_64-linux.xfs —
checks.x86_64-linux.zfs —
checks.x86_64-linux.zfs-encrypted-root —
checks.x86_64-linux.zfs-over-legacy —
checks.x86_64-linux.zfs-with-vdevs —