nixbot

builds
sign in

nix-community/disko build #163 failed

branch master · PR #1294 · commit ada6279db8 · · took 17m 31s · eval 1m 32s

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

1 failed
checks.x86_64-linux.bcachefs 17m 12s
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 906.51 seconds (timeout=900)
cleanup
kill QemuMachine (pid 71)
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.08 seconds)
52 succeeded ⚠ 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
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
1s
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.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
 54s
checks.aarch64-darwin.disko-doc 30s
checks.aarch64-darwin.treefmt 7s
checks.aarch64-linux.disko-doc 4s
checks.aarch64-linux.treefmt 2s
checks.x86_64-linux.boot-raid1 1m 42s
checks.x86_64-linux.btrfs-only-root-subvolume 1m 3s
checks.x86_64-linux.btrfs-subvolumes 1m 5s
checks.x86_64-linux.cli 1m 48s
checks.x86_64-linux.complex 1m 47s
checks.x86_64-linux.disko-doc 6s
checks.x86_64-linux.disko-install 10m 13s
checks.x86_64-linux.f2fs 57s
checks.x86_64-linux.gpt-bios-compat 53s
checks.x86_64-linux.gpt-name-with-special-chars 59s
checks.x86_64-linux.gpt-unformatted 54s
checks.x86_64-linux.gpt-uuid 2s
checks.x86_64-linux.hybrid 53s
checks.x86_64-linux.hybrid-mbr 59s
checks.x86_64-linux.hybrid-tmpfs-on-root 56s
checks.x86_64-linux.long-device-name 49s
checks.x86_64-linux.luks-btrfs-raid 1m 47s
checks.x86_64-linux.luks-btrfs-subvolumes 1m 46s
checks.x86_64-linux.luks-fido2 1m 21s
checks.x86_64-linux.luks-interactive-login 1m 35s
checks.x86_64-linux.luks-lvm 1m 46s
checks.x86_64-linux.luks-on-mdadm 1m 47s
checks.x86_64-linux.lvm-raid 1m 14s
checks.x86_64-linux.lvm-sizes-sort 54s
checks.x86_64-linux.lvm-thin 54s
checks.x86_64-linux.make-disk-image 53s
checks.x86_64-linux.make-disk-image-impure 14s
checks.x86_64-linux.mdadm 1m 15s
checks.x86_64-linux.mdadm-raid0 1m 15s
checks.x86_64-linux.mdadm-raid5-args 1m 14s
checks.x86_64-linux.module 1m 38s
checks.x86_64-linux.multi-device-no-deps 31s
checks.x86_64-linux.negative-size 27s
checks.x86_64-linux.non-root-zfs 1m 19s
checks.x86_64-linux.simple-efi 49s
checks.x86_64-linux.swap 59s
checks.x86_64-linux.tmpfs 48s
checks.x86_64-linux.treefmt 3s
checks.x86_64-linux.with-lib 50s
checks.x86_64-linux.xfs 51s
checks.x86_64-linux.zfs 1m 7s
checks.x86_64-linux.zfs-encrypted-root 54s
checks.x86_64-linux.zfs-over-legacy 56s
checks.x86_64-linux.zfs-with-vdevs 2m 38s
6 already built ⚠ 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
—
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.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 —