nix-community/disko #122

nix-community/disko build #122 failed ← #82 #124 →

branch master · PR #1208 · commit 985a22243c · 96d ago · took 16m 58s · eval 1m 39s

1 failed

status attribute duration

failed checks.x86_64-linux.bcachefs 16m 56s

failed attributes
status	attribute	duration
failed	`checks.x86_64-linux.bcachefs`	16m 56s
vm-test-run-disko-bcachefs: !!! File "<string>", line 84, in <module> !!! machine.wait_for_text("enter passphrase for /nix"); !!! !!! RequestedAssertionF … vm-test-run-disko-bcachefs: !!! File "<string>", line 84, in <module> !!! machine.wait_for_text("enter passphrase for /nix"); !!! !!! RequestedAssertionFailed: action timed out after 901.90 seconds (timeout=900) cleanup kill QemuMachine (pid 68) booted_machine # qemu-system-x86_64: terminating on signal 15 from pid 6 (/nix/store/60m4rxhg2fldqaak400c0lry96ijrzqn-python3-3.13.13/bin/python3.13) (finished: cleanup, in 0.09 seconds)

vm-test-run-disko-bcachefs: !!! File "<string>", line 84, in <module> !!! machine.wait_for_text("enter passphrase for /nix"); !!! !!! RequestedAssertionF …

vm-test-run-disko-bcachefs:
!!!   File "<string>", line 84, in <module>
!!!     machine.wait_for_text("enter passphrase for /nix");
!!! 
!!! RequestedAssertionFailed: action timed out after 901.90 seconds (timeout=900)
cleanup
kill QemuMachine (pid 68)
booted_machine # qemu-system-x86_64: terminating on signal 15 from pid 6 (/nix/store/60m4rxhg2fldqaak400c0lry96ijrzqn-python3-3.13.13/bin/python3.13)
(finished: cleanup, in 0.09 seconds)

58 succeeded ⚠ 7

succeeded attributes
status	attribute	duration
succeeded	`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	0s
succeeded	`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
succeeded	`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	0s
succeeded	`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	0s
succeeded	`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	0s
succeeded	`checks.x86_64-linux.mdadm-btrfs-wipe` mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.	0s
succeeded	`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	0s
succeeded	`checks.aarch64-darwin.checkJqSyntax`	0s
succeeded	`checks.aarch64-darwin.disko-doc`	0s
succeeded	`checks.aarch64-darwin.treefmt`	0s
succeeded	`checks.aarch64-linux.checkJqSyntax`	0s
succeeded	`checks.aarch64-linux.disko-doc`	0s
succeeded	`checks.aarch64-linux.treefmt`	0s
succeeded	`checks.x86_64-linux.boot-raid1`	0s
succeeded	`checks.x86_64-linux.btrfs-only-root-subvolume`	0s
succeeded	`checks.x86_64-linux.btrfs-subvolumes`	0s
succeeded	`checks.x86_64-linux.checkJqSyntax`	0s
succeeded	`checks.x86_64-linux.cli`	0s
succeeded	`checks.x86_64-linux.complex`	0s
succeeded	`checks.x86_64-linux.disko-doc`	0s
succeeded	`checks.x86_64-linux.disko-install`	0s
succeeded	`checks.x86_64-linux.f2fs`	0s
succeeded	`checks.x86_64-linux.gpt-bios-compat`	0s
succeeded	`checks.x86_64-linux.gpt-name-with-special-chars`	0s
succeeded	`checks.x86_64-linux.gpt-unformatted`	0s
succeeded	`checks.x86_64-linux.hybrid`	0s
succeeded	`checks.x86_64-linux.hybrid-mbr`	0s
succeeded	`checks.x86_64-linux.hybrid-tmpfs-on-root`	0s
succeeded	`checks.x86_64-linux.long-device-name`	0s
succeeded	`checks.x86_64-linux.luks-btrfs-raid`	0s
succeeded	`checks.x86_64-linux.luks-btrfs-subvolumes`	0s
succeeded	`checks.x86_64-linux.luks-fido2`	0s
succeeded	`checks.x86_64-linux.luks-interactive-login`	0s
succeeded	`checks.x86_64-linux.luks-lvm`	0s
succeeded	`checks.x86_64-linux.luks-on-mdadm`	0s
succeeded	`checks.x86_64-linux.lvm-raid`	0s
succeeded	`checks.x86_64-linux.lvm-sizes-sort`	0s
succeeded	`checks.x86_64-linux.lvm-thin`	0s
succeeded	`checks.x86_64-linux.make-disk-image`	0s
succeeded	`checks.x86_64-linux.make-disk-image-impure`	0s
succeeded	`checks.x86_64-linux.mdadm`	0s
succeeded	`checks.x86_64-linux.mdadm-raid0`	0s
succeeded	`checks.x86_64-linux.mdadm-raid5-args`	0s
succeeded	`checks.x86_64-linux.module`	0s
succeeded	`checks.x86_64-linux.multi-device-no-deps`	0s
succeeded	`checks.x86_64-linux.negative-size`	0s
succeeded	`checks.x86_64-linux.non-root-zfs`	0s
succeeded	`checks.x86_64-linux.simple-efi`	0s
succeeded	`checks.x86_64-linux.swap`	0s
succeeded	`checks.x86_64-linux.tmpfs`	0s
succeeded	`checks.x86_64-linux.treefmt`	0s
succeeded	`checks.x86_64-linux.with-lib`	0s
succeeded	`checks.x86_64-linux.xfs`	0s
succeeded	`checks.x86_64-linux.zfs`	0s
succeeded	`checks.x86_64-linux.zfs-encrypted-root`	0s
succeeded	`checks.x86_64-linux.zfs-multi-raidz3`	0s
succeeded	`checks.x86_64-linux.zfs-over-legacy`	0s
succeeded	`checks.x86_64-linux.zfs-with-vdevs`	0s