nixbot

builds
sign in

nix-community/disko build #188 succeeded

branch master · PR #1244 · commit 824c3d9629 · · took 9m 41s · eval 1m 31s

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

58 succeeded ⚠ 7
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
2s
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
0s
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
1s
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
  • 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
  • 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
43s
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
  • 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
  • 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
48s
checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
 51s
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
26s
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.bcache 1m 18s
checks.x86_64-linux.bcachefs 2m 27s
checks.x86_64-linux.bcache-validation 2s
checks.x86_64-linux.boot-raid1 1m 32s
checks.x86_64-linux.btrfs-only-root-subvolume 1m 1s
checks.x86_64-linux.btrfs-subvolumes 1m 3s
checks.x86_64-linux.cli 1m 47s
checks.x86_64-linux.complex 1m 48s
checks.x86_64-linux.disko-doc 12s
checks.x86_64-linux.disko-install 9m 14s
checks.x86_64-linux.f2fs 54s
checks.x86_64-linux.gpt-bios-compat 58s
checks.x86_64-linux.gpt-name-with-special-chars 1m 3s
checks.x86_64-linux.gpt-unformatted 56s
checks.x86_64-linux.hybrid 56s
checks.x86_64-linux.hybrid-mbr 1m 3s
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 45s
checks.x86_64-linux.luks-btrfs-subvolumes 1m 48s
checks.x86_64-linux.luks-fido2 1m 20s
checks.x86_64-linux.luks-interactive-login 1m 34s
checks.x86_64-linux.luks-lvm 1m 48s
checks.x86_64-linux.luks-on-mdadm 1m 46s
checks.x86_64-linux.luks-password-mismatch 43s
checks.x86_64-linux.lvm-raid 1m 11s
checks.x86_64-linux.lvm-sizes-sort 54s
checks.x86_64-linux.lvm-thin 54s
checks.x86_64-linux.make-disk-image 56s
checks.x86_64-linux.make-disk-image-impure 8s
checks.x86_64-linux.mdadm 1m 18s
checks.x86_64-linux.mdadm-raid0 1m 14s
checks.x86_64-linux.mdadm-raid5-args 1m 14s
checks.x86_64-linux.module 1m 37s
checks.x86_64-linux.multi-device-no-deps 36s
checks.x86_64-linux.negative-size 28s
checks.x86_64-linux.non-root-zfs 1m 21s
checks.x86_64-linux.simple-efi 54s
checks.x86_64-linux.swap 1m 7s
checks.x86_64-linux.tmpfs 55s
checks.x86_64-linux.treefmt 2s
checks.x86_64-linux.with-lib 58s
checks.x86_64-linux.xfs 55s
checks.x86_64-linux.zfs 1m 15s
checks.x86_64-linux.zfs-encrypted-root 1m 3s
checks.x86_64-linux.zfs-over-legacy 1m 2s
checks.x86_64-linux.zfs-with-vdevs 2m 45s
3 already built
loading…