nixbot

builds

nix-community/disko build #169 failed

branch master · PR #1273 · commit 1be57cb934 · · took 22m 34s · eval 2m 38s

eval warnings 8 kinds · 28 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
  • error ×2
  • error vmTools: the `kernel` argument (kernel-modules) has no ×2
  • warn The legacy table is outdated and should not be used. We recommend using the gpt type instead. ×10
  • warn stdenv.isDarwin is deprecated, use stdenv.hostPlatform.isDarwin instead ×1
  • 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
failed attributes
status attribute duration
failed checks.x86_64-linux.bcachefs 18m 50s
vm-test-run-disko-bcachefs: !!! File "<string>", line 79, in <module> !!! machine.wait_for_text("enter passphrase for /nix"); !!! !!! RequestedAssertionF …
vm-test-run-disko-bcachefs:
!!!   File "<string>", line 79, in <module>
!!!     machine.wait_for_text("enter passphrase for /nix");
!!! 
!!! RequestedAssertionFailed: action timed out after 904.77 seconds (timeout=900.0)
cleanup
kill QemuMachine (pid 117)
booted_machine # qemu-system-x86_64: terminating on signal 15 from pid 39 (/nix/store/d64q19q1xjdwfhqx6czvrjgrhq0n3lcc-python3-3.14.7/bin/python3.14)
(finished: cleanup, in 0.09 seconds)
failed eval checks.x86_64-linux.make-disk-image
error: … while calling the 'derivationStrict' builtin at «nix-internal»/derivation-internal.nix:37:12: 36| 37| strict = …
error:
       … while calling the 'derivationStrict' builtin
         at «nix-internal»/derivation-internal.nix:37:12:
           36|
           37|   strict = derivationStrict drvAttrs;
             |            ^
           38|

       … while evaluating derivation 'nixos-disko-images'
         whose name attribute is located at «github:NixOS/nixpkgs/02f5696b0e6097e589076d886b317b83ff0437d7?narHash=sha256-llGJbC0CcU8DfROr6mZjRJgMLQd/SKwfpzxJH/2lHO4%3D»/pkgs/stdenv/generic/make-derivation.nix:651:11

       … while evaluating attribute 'args' of derivation 'nixos-disko-images'
         at «github:NixOS/nixpkgs/02f5696b0e6097e589076d886b317b83ff0437d7?narHash=sha256-llGJbC0CcU8DfROr6mZjRJgMLQd/SKwfpzxJH/2lHO4%3D»/pkgs/build-support/vm/default.nix:414:9:
          413|         builder = "${bash}/bin/sh";
          414|         args = [
             |         ^
          415|           "-e"

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: vmTools: the `kernel` argument (kernel-modules) has no
       `target` attribute, so the kernel image filename cannot be determined.

       If you are passing a module tree (e.g. from `pkgs.aggregateModules`) to
       make extra modules available, pass it via `kernelModules` instead and
       keep `kernel` pointing at a real kernel derivation. Alternatively, pass
       `kernelImage` explicitly with the path of the bootable image relative
       to the `kernel` derivation output (e.g. "bzImage" or "Image").
failed eval checks.x86_64-linux.make-disk-image-impure
error: … while evaluating a branch condition at «string»:25:5: 24| v: 25| if !builtins.isAttrs v || isDrv v then …
error:
       … while evaluating a branch condition
         at «string»:25:5:
           24|     v:
           25|     if !builtins.isAttrs v || isDrv v then
             |     ^
           26|       v

       … in the left operand of the OR (||) operator
         at «string»:25:28:
           24|     v:
           25|     if !builtins.isAttrs v || isDrv v then
             |                            ^
           26|       v

       … while evaluating definitions from `/nix/store/4jfi5ykl9741kcmq866mf94dpzkgvkpp-source/lib/make-disk-image.nix':

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: vmTools: the `kernel` argument (kernel-modules) has no
       `target` attribute, so the kernel image filename cannot be determined.

       If you are passing a module tree (e.g. from `pkgs.aggregateModules`) to
       make extra modules available, pass it via `kernelModules` instead and
       keep `kernel` pointing at a real kernel derivation. Alternatively, pass
       `kernelImage` explicitly with the path of the bootable image relative
       to the `kernel` derivation output (e.g. "bzImage" or "Image").
failed checks.x86_64-linux.simple-efi 5m 55s
vm-test-run-disko-simple-efi: ) ^ File "/nix/store/q8bka5k1zvss9dd482k8ivsflp9lkmxw-nixos-test-driver-1.1/lib/python3.14/site-packages/test_driver/mac …
vm-test-run-disko-simple-efi:
    )
    ^
  File "/nix/store/q8bka5k1zvss9dd482k8ivsflp9lkmxw-nixos-test-driver-1.1/lib/python3.14/site-packages/test_driver/machine/__init__.py", line 983, in _execute
    self.connect()
    ~~~~~~~~~~~~^^
  File "/nix/store/q8bka5k1zvss9dd482k8ivsflp9lkmxw-nixos-test-driver-1.1/lib/python3.14/site-packages/test_driver/machine/__init__.py", line 1177, in connect
    raise RuntimeError("Shell disconnected")
RuntimeError: Shell disconnected
54 succeeded ⚠ 8
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
1s
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
1s
succeeded checks.x86_64-linux.disko-install
  • stdenv.isDarwin is deprecated, use stdenv.hostPlatform.isDarwin instead
21m 42s
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
9s
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
1m 51s
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
1m 56s
succeeded checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
1m 49s
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
42s
succeeded checks.aarch64-darwin.checkJqSyntax 2s
succeeded checks.aarch64-darwin.disko-doc 9s
succeeded checks.aarch64-darwin.treefmt 5s
succeeded checks.aarch64-linux.checkJqSyntax 1s
succeeded checks.aarch64-linux.disko-doc 6s
succeeded checks.aarch64-linux.treefmt 3s
succeeded checks.x86_64-linux.boot-raid1 3m 28s
succeeded checks.x86_64-linux.btrfs-only-root-subvolume 2m 50s
succeeded checks.x86_64-linux.btrfs-subvolumes 2m 52s
succeeded checks.x86_64-linux.checkJqSyntax 2s
succeeded checks.x86_64-linux.cli 3m 34s
succeeded checks.x86_64-linux.complex 3m 35s
succeeded checks.x86_64-linux.disko-doc 59s
succeeded checks.x86_64-linux.f2fs 2m 25s
succeeded checks.x86_64-linux.gpt-bios-compat 2m 26s
succeeded checks.x86_64-linux.gpt-name-with-special-chars 2m 20s
succeeded checks.x86_64-linux.gpt-unformatted 2m 24s
succeeded checks.x86_64-linux.hybrid 2m 21s
succeeded checks.x86_64-linux.hybrid-mbr 2m 27s
succeeded checks.x86_64-linux.hybrid-tmpfs-on-root 2m 16s
succeeded checks.x86_64-linux.long-device-name 1m 59s
succeeded checks.x86_64-linux.luks-btrfs-raid 2m 55s
succeeded checks.x86_64-linux.luks-btrfs-subvolumes 2m 49s
succeeded checks.x86_64-linux.luks-fido2 2m 22s
succeeded checks.x86_64-linux.luks-interactive-login 2m 23s
succeeded checks.x86_64-linux.luks-lvm 2m 47s
succeeded checks.x86_64-linux.luks-on-mdadm 2m 44s
succeeded checks.x86_64-linux.lvm-raid 2m 5s
succeeded checks.x86_64-linux.lvm-sizes-sort 1m 31s
succeeded checks.x86_64-linux.lvm-thin 1m 37s
succeeded checks.x86_64-linux.mdadm 2m 6s
succeeded checks.x86_64-linux.mdadm-raid0 2m 3s
succeeded checks.x86_64-linux.mdadm-raid5-args 2m 4s
succeeded checks.x86_64-linux.module 2m 6s
succeeded checks.x86_64-linux.multi-device-no-deps 1m 9s
succeeded checks.x86_64-linux.negative-size 54s
succeeded checks.x86_64-linux.non-root-zfs 2m 0s
succeeded checks.x86_64-linux.swap 1m 35s
succeeded checks.x86_64-linux.tmpfs 1m 13s
succeeded checks.x86_64-linux.treefmt 13s
succeeded checks.x86_64-linux.with-lib 1m 25s
succeeded checks.x86_64-linux.xfs 1m 23s
succeeded checks.x86_64-linux.zfs 1m 29s
succeeded checks.x86_64-linux.zfs-encrypted-root 1m 19s
succeeded checks.x86_64-linux.zfs-over-legacy 1m 14s
succeeded checks.x86_64-linux.zfs-with-vdevs 2m 48s