nixbot

builds
sign in

nix-community/disko build #201 failed

branch master · PR #1273 · commit 1fdefc205b · · took 20m 21s · eval 2m 1s

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

4 failed
checks.aarch64-darwin.treefmt 5s
treefmt: HasCallStack backtrace: collectBacktraces, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:169:13 in ghc-internal:GHC.Internal.Excepti … 
treefmt:
HasCallStack backtrace:
  collectBacktraces, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:169:13 in ghc-internal:GHC.Internal.Exception
  toExceptionWithBacktrace, called at libraries/ghc-internal/src/GHC/Internal/IO.hs:260:11 in ghc-internal:GHC.Internal.IO
  throwIO, called at libraries/ghc-internal/src/GHC/Internal/Control/Exception/Base.hs:195:43 in ghc-internal:GHC.Internal.Control.Exception.Base
traversed 157 files
emitted 127 files for processing
formatted 0 files (0 changed) in 1.656s
Error: failed to finalise formatting: formatting failures detected
checks.aarch64-linux.treefmt 3s
treefmt: HasCallStack backtrace: collectBacktraces, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:169:13 in ghc-internal:GHC.Internal.Excepti … 
treefmt:
HasCallStack backtrace:
  collectBacktraces, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:169:13 in ghc-internal:GHC.Internal.Exception
  toExceptionWithBacktrace, called at libraries/ghc-internal/src/GHC/Internal/IO.hs:260:11 in ghc-internal:GHC.Internal.IO
  throwIO, called at libraries/ghc-internal/src/GHC/Internal/Control/Exception/Base.hs:195:43 in ghc-internal:GHC.Internal.Control.Exception.Base
traversed 157 files
emitted 127 files for processing
formatted 0 files (0 changed) in 1.215s
Error: failed to finalise formatting: formatting failures detected
checks.x86_64-linux.bcachefs 19m 12s
vm-test-run-disko-bcachefs: !!! File "<string>", line 79, in <module> !!! machine.wait_for_text("enter passphrase for /home"); !!! !!! RequestedAssertion … 
vm-test-run-disko-bcachefs:
!!!   File "<string>", line 79, in <module>
!!!     machine.wait_for_text("enter passphrase for /home");
!!! 
!!! RequestedAssertionFailed: action timed out after 907.93 seconds (timeout=900.0)
cleanup
kill QemuMachine (pid 124)
booted_machine # qemu-system-x86_64: terminating on signal 15 from pid 39 (/nix/store/xahxrjs30p3mw0a42bqg9ikgkikskw8m-python3-3.14.8/bin/python3.14)
(finished: cleanup, in 0.08 seconds)
checks.x86_64-linux.treefmt 9s
treefmt: HasCallStack backtrace: collectBacktraces, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:169:13 in ghc-internal:GHC.Internal.Excepti … 
treefmt:
HasCallStack backtrace:
  collectBacktraces, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:169:13 in ghc-internal:GHC.Internal.Exception
  toExceptionWithBacktrace, called at libraries/ghc-internal/src/GHC/Internal/IO.hs:260:11 in ghc-internal:GHC.Internal.IO
  throwIO, called at libraries/ghc-internal/src/GHC/Internal/Control/Exception/Base.hs:195:43 in ghc-internal:GHC.Internal.Control.Exception.Base
traversed 157 files
emitted 127 files for processing
formatted 0 files (0 changed) in 1.01s
Error: failed to finalise formatting: formatting failures detected
58 succeeded ⚠ 6
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
2s
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
2m 30s
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
2m 28s
checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
 2m 30s
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
1m 25s
checks.aarch64-darwin.checkJqSyntax 3s
checks.aarch64-darwin.disko-doc 16s
checks.aarch64-darwin.jsonTypes 3s
checks.aarch64-linux.checkJqSyntax 2s
checks.aarch64-linux.disko-doc 8s
checks.x86_64-linux.boot-raid1 3m 40s
checks.x86_64-linux.btrfs-only-root-subvolume 3m 4s
checks.x86_64-linux.btrfs-subvolumes 3m 7s
checks.x86_64-linux.checkJqSyntax 1s
checks.x86_64-linux.cli 3m 50s
checks.x86_64-linux.complex 3m 51s
checks.x86_64-linux.disko-doc 19s
checks.x86_64-linux.disko-install 19m 30s
checks.x86_64-linux.f2fs 3m 1s
checks.x86_64-linux.gpt-bios-compat 2m 51s
checks.x86_64-linux.gpt-name-with-special-chars 3m 8s
checks.x86_64-linux.gpt-unformatted 2m 48s
checks.x86_64-linux.hybrid 2m 49s
checks.x86_64-linux.hybrid-mbr 2m 58s
checks.x86_64-linux.hybrid-tmpfs-on-root 2m 45s
checks.x86_64-linux.long-device-name 2m 33s
checks.x86_64-linux.luks-btrfs-raid 3m 37s
checks.x86_64-linux.luks-btrfs-subvolumes 3m 35s
checks.x86_64-linux.luks-detached-header 2m 34s
checks.x86_64-linux.luks-fido2 3m 4s
checks.x86_64-linux.luks-interactive-login 3m 18s
checks.x86_64-linux.luks-lvm 3m 14s
checks.x86_64-linux.luks-multiple 3m 46s
checks.x86_64-linux.luks-on-mdadm 3m 26s
checks.x86_64-linux.luks-password-mismatch 2m 28s
checks.x86_64-linux.lvm-raid 2m 47s
checks.x86_64-linux.lvm-sizes-sort 2m 5s
checks.x86_64-linux.lvm-thin 2m 21s
checks.x86_64-linux.make-disk-image 2m 34s
checks.x86_64-linux.make-disk-image-impure 1m 55s
checks.x86_64-linux.mdadm 2m 47s
checks.x86_64-linux.mdadm-raid0 2m 39s
checks.x86_64-linux.mdadm-raid5-args 2m 39s
checks.x86_64-linux.module 2m 41s
checks.x86_64-linux.multi-device-no-deps 1m 36s
checks.x86_64-linux.negative-size 1m 30s
checks.x86_64-linux.non-root-zfs 2m 38s
checks.x86_64-linux.simple-efi 1m 40s
checks.x86_64-linux.swap 2m 17s
checks.x86_64-linux.tmpfs 1m 54s
checks.x86_64-linux.vm-with-disko-swap 3s
checks.x86_64-linux.with-lib 2m 6s
checks.x86_64-linux.xfs 2m 1s
checks.x86_64-linux.zfs 2m 9s
checks.x86_64-linux.zfs-encrypted-root 2m 5s
checks.x86_64-linux.zfs-over-legacy 2m 2s
checks.x86_64-linux.zfs-with-vdevs 3m 37s