nixbot

builds

nix-community/disko build #173 failed

branch master · PR #1273 · commit a422c2c4e6 · · took 12m 13s · eval 1m 49s

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

2 failed
failed attributes
status attribute duration
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/0a3468a402c449992505b6a9fc5b06580141b750?narHash=sha256-nlKgrm0dsVhOSopKheVBCcOpiIticufPPVLdVOI0euA%3D»/pkgs/stdenv/generic/make-derivation.nix:651:11

       … while evaluating attribute 'args' of derivation 'nixos-disko-images'
         at «github:NixOS/nixpkgs/0a3468a402c449992505b6a9fc5b06580141b750?narHash=sha256-nlKgrm0dsVhOSopKheVBCcOpiIticufPPVLdVOI0euA%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/javbgjy65bc6hxvawhm5zfrps5qxvhrg-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").
51 succeeded ⚠ 5
succeeded attributes
status attribute duration
succeeded checks.x86_64-linux.disko-install
  • stdenv.isDarwin is deprecated, use stdenv.hostPlatform.isDarwin instead
11m 21s
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 12s
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 9s
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 23s
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
29s
succeeded checks.aarch64-darwin.disko-doc 10s
succeeded checks.aarch64-darwin.treefmt 3s
succeeded checks.aarch64-linux.disko-doc 5s
succeeded checks.aarch64-linux.treefmt 2s
succeeded checks.x86_64-linux.bcachefs 3m 2s
succeeded checks.x86_64-linux.boot-raid1 2m 15s
succeeded checks.x86_64-linux.btrfs-only-root-subvolume 1m 36s
succeeded checks.x86_64-linux.btrfs-subvolumes 1m 38s
succeeded checks.x86_64-linux.cli 2m 32s
succeeded checks.x86_64-linux.complex 2m 33s
succeeded checks.x86_64-linux.disko-doc 9s
succeeded checks.x86_64-linux.f2fs 1m 32s
succeeded checks.x86_64-linux.gpt-bios-compat 1m 34s
succeeded checks.x86_64-linux.gpt-name-with-special-chars 1m 42s
succeeded checks.x86_64-linux.gpt-unformatted 1m 28s
succeeded checks.x86_64-linux.hybrid 1m 31s
succeeded checks.x86_64-linux.hybrid-mbr 1m 36s
succeeded checks.x86_64-linux.hybrid-tmpfs-on-root 1m 27s
succeeded checks.x86_64-linux.long-device-name 1m 16s
succeeded checks.x86_64-linux.luks-btrfs-raid 2m 18s
succeeded checks.x86_64-linux.luks-btrfs-subvolumes 2m 25s
succeeded checks.x86_64-linux.luks-fido2 1m 56s
succeeded checks.x86_64-linux.luks-interactive-login 2m 9s
succeeded checks.x86_64-linux.luks-lvm 2m 17s
succeeded checks.x86_64-linux.luks-on-mdadm 2m 23s
succeeded checks.x86_64-linux.luks-password-mismatch 1m 32s
succeeded checks.x86_64-linux.lvm-raid 1m 40s
succeeded checks.x86_64-linux.lvm-sizes-sort 1m 17s
succeeded checks.x86_64-linux.lvm-thin 1m 18s
succeeded checks.x86_64-linux.mdadm 1m 47s
succeeded checks.x86_64-linux.mdadm-raid0 1m 40s
succeeded checks.x86_64-linux.mdadm-raid5-args 1m 41s
succeeded checks.x86_64-linux.module 1m 52s
succeeded checks.x86_64-linux.multi-device-no-deps 37s
succeeded checks.x86_64-linux.negative-size 31s
succeeded checks.x86_64-linux.non-root-zfs 1m 45s
succeeded checks.x86_64-linux.simple-efi 54s
succeeded checks.x86_64-linux.swap 1m 22s
succeeded checks.x86_64-linux.tmpfs 1m 5s
succeeded checks.x86_64-linux.treefmt 5s
succeeded checks.x86_64-linux.with-lib 1m 5s
succeeded checks.x86_64-linux.xfs 1m 11s
succeeded checks.x86_64-linux.zfs 1m 21s
succeeded checks.x86_64-linux.zfs-encrypted-root 1m 11s
succeeded checks.x86_64-linux.zfs-over-legacy 1m 14s
succeeded checks.x86_64-linux.zfs-with-vdevs 2m 52s
6 already built ⚠ 3
skipped attributes
status attribute duration
skipped local 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
skipped local 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
skipped local 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
skipped local checks.aarch64-darwin.checkJqSyntax
skipped local checks.aarch64-linux.checkJqSyntax
skipped local checks.x86_64-linux.checkJqSyntax