nixbot

builds
sign in

nix-community/disko build #216 failed

branch master · PR #1273 · commit 0c03f62225 · · took 24m 47s · eval 1m 29s

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

4 failed
checks.aarch64-darwin.treefmt 6s
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.758s
Error: failed to finalise formatting: formatting failures detected
checks.aarch64-linux.treefmt 44s
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 17.939s
Error: failed to finalise formatting: formatting failures detected
checks.x86_64-linux.bcachefs 19m 9s
vm-test-run-disko-bcachefs: [994.89s] !!! File "<string>", line 81, in <module> [994.89s] !!! machine.wait_for_text("enter passphrase for /nix"); [994.89s … 
vm-test-run-disko-bcachefs:
[994.89s] !!!   File "<string>", line 81, in <module>
[994.89s] !!!     machine.wait_for_text("enter passphrase for /nix");
[994.89s] !!! 
[994.89s] !!! RequestedAssertionFailed: action timed out after 905.29 seconds (timeout=900.0)
[994.89s] cleanup
[994.89s] kill QemuMachine (pid 112)
booted_machine # qemu-system-x86_64: terminating on signal 15 from pid 39 (/nix/store/bya4ansy58az5133kryqp2cvrxbnz8qy-python3-3.14.10/bin/python3.14)
[994.96s] (finished: cleanup, in 0.07 seconds)
checks.x86_64-linux.treefmt 18s
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 430ms
Error: failed to finalise formatting: formatting failures detected
58 succeeded ⚠ 7
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
1s
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
10s
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.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 47s
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 45s
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 13s
checks.aarch64-darwin.checkJqSyntax 1s
checks.aarch64-darwin.disko-doc 19s
checks.aarch64-linux.checkJqSyntax 21s
checks.aarch64-linux.disko-doc 1m 13s
checks.x86_64-linux.boot-raid1 3m 50s
checks.x86_64-linux.btrfs-only-root-subvolume 3m 13s
checks.x86_64-linux.btrfs-subvolumes 3m 14s
checks.x86_64-linux.checkJqSyntax 1s
checks.x86_64-linux.cli 3m 57s
checks.x86_64-linux.complex 3m 53s
checks.x86_64-linux.disko-doc 19s
checks.x86_64-linux.disko-install 24m 5s
checks.x86_64-linux.f2fs 3m 11s
checks.x86_64-linux.gpt-bios-compat 3m 9s
checks.x86_64-linux.gpt-name-with-special-chars 3m 11s
checks.x86_64-linux.gpt-unformatted 3m 7s
checks.x86_64-linux.hybrid 3m 7s
checks.x86_64-linux.hybrid-mbr 3m 11s
checks.x86_64-linux.hybrid-tmpfs-on-root 2m 55s
checks.x86_64-linux.long-device-name 2m 50s
checks.x86_64-linux.luks-btrfs-raid 3m 45s
checks.x86_64-linux.luks-btrfs-subvolumes 3m 42s
checks.x86_64-linux.luks-detached-header 2m 54s
checks.x86_64-linux.luks-fido2 3m 14s
checks.x86_64-linux.luks-interactive-login 3m 29s
checks.x86_64-linux.luks-lvm 3m 35s
checks.x86_64-linux.luks-multiple 4m 7s
checks.x86_64-linux.luks-on-mdadm 3m 34s
checks.x86_64-linux.luks-password-mismatch 2m 37s
checks.x86_64-linux.lvm-raid 2m 47s
checks.x86_64-linux.lvm-sizes-sort 2m 39s
checks.x86_64-linux.lvm-thin 2m 34s
checks.x86_64-linux.make-disk-image 2m 41s
checks.x86_64-linux.make-disk-image-impure 1m 59s
checks.x86_64-linux.mdadm 2m 51s
checks.x86_64-linux.mdadm-raid0 2m 44s
checks.x86_64-linux.mdadm-raid5-args 2m 45s
checks.x86_64-linux.module 3m 2s
checks.x86_64-linux.multi-device-no-deps 2m 11s
checks.x86_64-linux.negative-size 2m 4s
checks.x86_64-linux.non-root-zfs 2m 38s
checks.x86_64-linux.simple-efi 2m 14s
checks.x86_64-linux.swap 2m 21s
checks.x86_64-linux.tmpfs 2m 12s
checks.x86_64-linux.vm-with-disko-swap 4s
checks.x86_64-linux.with-lib 2m 12s
checks.x86_64-linux.xfs 2m 8s
checks.x86_64-linux.zfs 2m 19s
checks.x86_64-linux.zfs-encrypted-root 2m 10s
checks.x86_64-linux.zfs-over-legacy 2m 8s
checks.x86_64-linux.zfs-with-vdevs 3m 50s