nixbot

builds
sign in

nix-community/disko build #192 succeeded

branch gh-readonly-queue/master/pr-1281-33d5b13d6cd8b361c8041f77426fa520dddb9217 · commit 7d4804ad8d · · took 10m 4s · eval 1m 25s

eval warnings 5 kinds · 23 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," ×10
  • warn The legacy table is outdated and should not be used. We recommend using the gpt type instead. ×10
  • 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

53 succeeded ⚠ 3
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
40s
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
41s
checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
 49s
checks.aarch64-darwin.disko-doc 10s
checks.aarch64-darwin.treefmt 2s
checks.aarch64-linux.disko-doc 4s
checks.aarch64-linux.treefmt 2s
checks.x86_64-linux.bcachefs 2m 22s
checks.x86_64-linux.boot-raid1 1m 26s
checks.x86_64-linux.btrfs-only-root-subvolume 50s
checks.x86_64-linux.btrfs-subvolumes 52s
checks.x86_64-linux.cli 1m 39s
checks.x86_64-linux.complex 1m 33s
checks.x86_64-linux.disko-doc 5s
checks.x86_64-linux.disko-install 9m 42s
checks.x86_64-linux.f2fs 48s
checks.x86_64-linux.gpt-bios-compat 48s
checks.x86_64-linux.gpt-name-with-special-chars 1m 0s
checks.x86_64-linux.gpt-unformatted 59s
checks.x86_64-linux.hybrid 56s
checks.x86_64-linux.hybrid-mbr 1m 2s
checks.x86_64-linux.hybrid-tmpfs-on-root 57s
checks.x86_64-linux.long-device-name 50s
checks.x86_64-linux.luks-btrfs-raid 1m 44s
checks.x86_64-linux.luks-btrfs-subvolumes 1m 42s
checks.x86_64-linux.luks-detached-header 49s
checks.x86_64-linux.luks-fido2 1m 20s
checks.x86_64-linux.luks-interactive-login 1m 31s
checks.x86_64-linux.luks-lvm 1m 49s
checks.x86_64-linux.luks-multiple 2m 9s
checks.x86_64-linux.luks-on-mdadm 1m 52s
checks.x86_64-linux.lvm-raid 1m 10s
checks.x86_64-linux.lvm-sizes-sort 51s
checks.x86_64-linux.lvm-thin 53s
checks.x86_64-linux.make-disk-image 39s
checks.x86_64-linux.make-disk-image-impure 7s
checks.x86_64-linux.mdadm 1m 15s
checks.x86_64-linux.mdadm-raid0 1m 10s
checks.x86_64-linux.mdadm-raid5-args 1m 13s
checks.x86_64-linux.module 1m 37s
checks.x86_64-linux.multi-device-no-deps 31s
checks.x86_64-linux.negative-size 24s
checks.x86_64-linux.non-root-zfs 1m 20s
checks.x86_64-linux.simple-efi 50s
checks.x86_64-linux.swap 1m 5s
checks.x86_64-linux.tmpfs 55s
checks.x86_64-linux.treefmt 1s
checks.x86_64-linux.with-lib 54s
checks.x86_64-linux.xfs 52s
checks.x86_64-linux.zfs 1m 11s
checks.x86_64-linux.zfs-encrypted-root 57s
checks.x86_64-linux.zfs-over-legacy 58s
checks.x86_64-linux.zfs-with-vdevs 2m 39s
8 already built ⚠ 4
checks.aarch64-darwin.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.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.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-linux.checkJqSyntax —
checks.x86_64-linux.checkJqSyntax —
checks.x86_64-linux.luks-password-mismatch —