nixbot

builds

nix-community/disko build #181 failed

branch master · PR #1273 · commit 1306c7296a · · took 19m 46s · eval 1m 34s

eval warnings 8 kinds · 26 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
  • 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. ×9
  • 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

3 failed
failed attributes
status attribute duration
failed checks.x86_64-linux.bcachefs 19m 15s
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 909.60 seconds (timeout=900.0)
cleanup
kill QemuMachine (pid 116)
booted_machine # qemu-system-x86_64: terminating on signal 15 from pid 39 (/nix/store/lb41b0anx1f98y9y5s9mdv97gjgsq740-python3-3.14.7/bin/python3.14)
(finished: cleanup, in 0.07 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/7dd199b0e2993e37b4775ed66b1c291699608c9f?narHash=sha256-o9ZUW4SlEAvFPIyJWnqChhOT/VHpHg8TAvEgmqK1fSI%3D»/pkgs/stdenv/generic/make-derivation.nix:651:11

       … while evaluating attribute 'args' of derivation 'nixos-disko-images'
         at «github:NixOS/nixpkgs/7dd199b0e2993e37b4775ed66b1c291699608c9f?narHash=sha256-o9ZUW4SlEAvFPIyJWnqChhOT/VHpHg8TAvEgmqK1fSI%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/bfkg7789idbll36jcqnmyv5cw6vw9nh6-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").
56 succeeded ⚠ 7
succeeded attributes
status attribute duration
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
12m 51s
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
1s
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
2m 44s
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
2m 50s
succeeded checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
2m 28s
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
1m 30s
succeeded checks.aarch64-darwin.checkJqSyntax 2s
succeeded checks.aarch64-darwin.disko-doc 12s
succeeded checks.aarch64-darwin.jsonTypes 16s
succeeded checks.aarch64-darwin.treefmt 35s
succeeded checks.aarch64-linux.checkJqSyntax 1s
succeeded checks.aarch64-linux.disko-doc 5s
succeeded checks.aarch64-linux.treefmt 3s
succeeded checks.x86_64-linux.boot-raid1 4m 0s
succeeded checks.x86_64-linux.btrfs-only-root-subvolume 3m 20s
succeeded checks.x86_64-linux.btrfs-subvolumes 3m 22s
succeeded checks.x86_64-linux.checkJqSyntax 1s
succeeded checks.x86_64-linux.cli 3m 54s
succeeded checks.x86_64-linux.complex 3m 56s
succeeded checks.x86_64-linux.disko-doc 39s
succeeded checks.x86_64-linux.f2fs 3m 13s
succeeded checks.x86_64-linux.gpt-bios-compat 3m 9s
succeeded checks.x86_64-linux.gpt-name-with-special-chars 3m 20s
succeeded checks.x86_64-linux.gpt-unformatted 3m 3s
succeeded checks.x86_64-linux.hybrid 3m 7s
succeeded checks.x86_64-linux.hybrid-mbr 3m 8s
succeeded checks.x86_64-linux.hybrid-tmpfs-on-root 3m 2s
succeeded checks.x86_64-linux.long-device-name 2m 46s
succeeded checks.x86_64-linux.luks-btrfs-raid 3m 42s
succeeded checks.x86_64-linux.luks-btrfs-subvolumes 3m 43s
succeeded checks.x86_64-linux.luks-fido2 3m 14s
succeeded checks.x86_64-linux.luks-interactive-login 3m 22s
succeeded checks.x86_64-linux.luks-lvm 3m 43s
succeeded checks.x86_64-linux.luks-on-mdadm 3m 38s
succeeded checks.x86_64-linux.luks-password-mismatch 2m 29s
succeeded checks.x86_64-linux.lvm-raid 2m 47s
succeeded checks.x86_64-linux.lvm-sizes-sort 2m 32s
succeeded checks.x86_64-linux.lvm-thin 2m 37s
succeeded checks.x86_64-linux.mdadm 2m 53s
succeeded checks.x86_64-linux.mdadm-raid0 2m 48s
succeeded checks.x86_64-linux.mdadm-raid5-args 2m 45s
succeeded checks.x86_64-linux.module 3m 6s
succeeded checks.x86_64-linux.multi-device-no-deps 2m 9s
succeeded checks.x86_64-linux.negative-size 2m 3s
succeeded checks.x86_64-linux.non-root-zfs 2m 46s
succeeded checks.x86_64-linux.simple-efi 2m 14s
succeeded checks.x86_64-linux.swap 2m 25s
succeeded checks.x86_64-linux.tmpfs 2m 7s
succeeded checks.x86_64-linux.treefmt 22s
succeeded checks.x86_64-linux.with-lib 2m 7s
succeeded checks.x86_64-linux.xfs 2m 9s
succeeded checks.x86_64-linux.zfs 2m 25s
succeeded checks.x86_64-linux.zfs-encrypted-root 2m 10s
succeeded checks.x86_64-linux.zfs-over-legacy 2m 10s
succeeded checks.x86_64-linux.zfs-with-vdevs 3m 50s