nixbot

builds
sign in

nix-community/disko build #211 failed

branch master · PR #1208 · commit 8546996901 · · took 18m 1s · eval 1m 22s

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 45s
vm-test-run-disko-bcachefs: !!! File "<string>", line 86, in <module> !!! machine.wait_for_text("enter passphrase for /nix"); !!! !!! RequestedAssertionF … 
vm-test-run-disko-bcachefs:
!!!   File "<string>", line 86, in <module>
!!!     machine.wait_for_text("enter passphrase for /nix");
!!! 
!!! RequestedAssertionFailed: action timed out after 900.83 seconds (timeout=900)
cleanup
kill QemuMachine (pid 73)
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.16 seconds)
52 succeeded ⚠ 2
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 13s
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 13s
checks.aarch64-darwin.disko-doc 21s
checks.aarch64-darwin.treefmt 6s
checks.aarch64-linux.disko-doc 5s
checks.aarch64-linux.treefmt 3s
checks.x86_64-linux.boot-raid1 2m 7s
checks.x86_64-linux.btrfs-only-root-subvolume 1m 30s
checks.x86_64-linux.btrfs-subvolumes 1m 42s
checks.x86_64-linux.cli 2m 26s
checks.x86_64-linux.complex 2m 26s
checks.x86_64-linux.disko-doc 22s
checks.x86_64-linux.disko-install 2m 42s
checks.x86_64-linux.f2fs 1m 34s
checks.x86_64-linux.gpt-bios-compat 1m 26s
checks.x86_64-linux.gpt-name-with-special-chars 1m 32s
checks.x86_64-linux.gpt-unformatted 1m 31s
checks.x86_64-linux.hybrid 1m 31s
checks.x86_64-linux.hybrid-mbr 1m 27s
checks.x86_64-linux.hybrid-tmpfs-on-root 1m 29s
checks.x86_64-linux.long-device-name 1m 19s
checks.x86_64-linux.luks-btrfs-raid 2m 21s
checks.x86_64-linux.luks-btrfs-subvolumes 2m 10s
checks.x86_64-linux.luks-detached-header 1m 14s
checks.x86_64-linux.luks-fido2 1m 36s
checks.x86_64-linux.luks-interactive-login 1m 55s
checks.x86_64-linux.luks-lvm 2m 5s
checks.x86_64-linux.luks-multiple 2m 40s
checks.x86_64-linux.luks-on-mdadm 2m 6s
checks.x86_64-linux.lvm-raid 1m 25s
checks.x86_64-linux.lvm-sizes-sort 1m 4s
checks.x86_64-linux.lvm-thin 1m 8s
checks.x86_64-linux.make-disk-image 50s
checks.x86_64-linux.make-disk-image-impure 13s
checks.x86_64-linux.mdadm 1m 24s
checks.x86_64-linux.mdadm-raid0 1m 21s
checks.x86_64-linux.mdadm-raid5-args 1m 22s
checks.x86_64-linux.module 1m 43s
checks.x86_64-linux.multi-device-no-deps 38s
checks.x86_64-linux.negative-size 30s
checks.x86_64-linux.non-root-zfs 1m 29s
checks.x86_64-linux.simple-efi 52s
checks.x86_64-linux.swap 1m 5s
checks.x86_64-linux.tmpfs 51s
checks.x86_64-linux.treefmt 3s
checks.x86_64-linux.with-lib 53s
checks.x86_64-linux.xfs 56s
checks.x86_64-linux.zfs 1m 12s
checks.x86_64-linux.zfs-encrypted-root 1m 0s
checks.x86_64-linux.zfs-multi-raidz3 7m 0s
checks.x86_64-linux.zfs-over-legacy 1m 1s
checks.x86_64-linux.zfs-with-vdevs 2m 44s
10 already built ⚠ 5
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.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
 —
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 —
checks.x86_64-linux.vm-with-disko-swap —