nixbot

builds
sign in

nix-community/disko build #170 failed

branch master · PR #1273 · commit 6e40301e4f · · took 26m 42s · eval 2m 12s

eval warnings 8 kinds · 26 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
  • error ×2
  • error vmTools: the `kernel` argument (kernel-modules) has no ×2
  • warn The legacy table is outdated and should not be used. We recommend using the gpt type instead. ×9
  • warn stdenv.isDarwin is deprecated, use stdenv.hostPlatform.isDarwin instead ×1
  • 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

1 failed
checks.x86_64-linux.bcachefs 15m 3s
vm-test-run-disko-bcachefs: !!! File "<string>", line 77, in <module> !!! machine.wait_for_text("enter passphrase for /home"); !!! !!! RequestedAssertion … 
vm-test-run-disko-bcachefs:
!!!   File "<string>", line 77, in <module>
!!!     machine.wait_for_text("enter passphrase for /home");
!!! 
!!! RequestedAssertionFailed: action timed out after 914.78 seconds (timeout=900.0)
cleanup
kill QemuMachine (pid 113)
booted_machine # qemu-system-x86_64: terminating on signal 15 from pid 39 (/nix/store/d64q19q1xjdwfhqx6czvrjgrhq0n3lcc-python3-3.14.7/bin/python3.14)
(finished: cleanup, in 0.08 seconds)
55 succeeded ⚠ 7
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
1s
checks.x86_64-linux.disko-install
  • stdenv.isDarwin is deprecated, use stdenv.hostPlatform.isDarwin instead
 13m 5s
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
2s
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
1m 9s
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
1m 9s
checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
 1m 21s
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
27s
checks.aarch64-darwin.checkJqSyntax 9s
checks.aarch64-darwin.disko-doc 13s
checks.aarch64-darwin.jsonTypes 9s
checks.aarch64-darwin.treefmt 9s
checks.aarch64-linux.checkJqSyntax 1s
checks.aarch64-linux.disko-doc 7s
checks.aarch64-linux.treefmt 3s
checks.x86_64-linux.boot-raid1 2m 8s
checks.x86_64-linux.btrfs-only-root-subvolume 1m 30s
checks.x86_64-linux.btrfs-subvolumes 1m 33s
checks.x86_64-linux.checkJqSyntax 1s
checks.x86_64-linux.cli 2m 17s
checks.x86_64-linux.complex 2m 16s
checks.x86_64-linux.disko-doc 19s
checks.x86_64-linux.f2fs 1m 13s
checks.x86_64-linux.gpt-bios-compat 1m 11s
checks.x86_64-linux.gpt-name-with-special-chars 1m 20s
checks.x86_64-linux.gpt-unformatted 1m 15s
checks.x86_64-linux.hybrid 1m 16s
checks.x86_64-linux.hybrid-mbr 1m 18s
checks.x86_64-linux.hybrid-tmpfs-on-root 1m 15s
checks.x86_64-linux.long-device-name 1m 14s
checks.x86_64-linux.luks-btrfs-raid 2m 10s
checks.x86_64-linux.luks-btrfs-subvolumes 2m 5s
checks.x86_64-linux.luks-fido2 1m 42s
checks.x86_64-linux.luks-interactive-login 2m 0s
checks.x86_64-linux.luks-lvm 2m 13s
checks.x86_64-linux.luks-on-mdadm 2m 8s
checks.x86_64-linux.lvm-raid 1m 28s
checks.x86_64-linux.lvm-sizes-sort 1m 13s
checks.x86_64-linux.lvm-thin 1m 15s
checks.x86_64-linux.mdadm 1m 34s
checks.x86_64-linux.mdadm-raid0 1m 32s
checks.x86_64-linux.mdadm-raid5-args 1m 36s
checks.x86_64-linux.module 1m 45s
checks.x86_64-linux.multi-device-no-deps 35s
checks.x86_64-linux.negative-size 28s
checks.x86_64-linux.non-root-zfs 1m 42s
checks.x86_64-linux.simple-efi 50s
checks.x86_64-linux.swap 1m 19s
checks.x86_64-linux.tmpfs 1m 0s
checks.x86_64-linux.treefmt 4s
checks.x86_64-linux.with-lib 1m 8s
checks.x86_64-linux.xfs 1m 8s
checks.x86_64-linux.zfs 1m 20s
checks.x86_64-linux.zfs-encrypted-root 1m 8s
checks.x86_64-linux.zfs-over-legacy 1m 9s
checks.x86_64-linux.zfs-with-vdevs 2m 57s