nixbot

builds

nix-community/disko build #180 failed

branch master · PR #1273 · commit 3d1dccadce · · took 30m 26s · eval 1m 40s

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

3 failed
failed attributes
status attribute duration
failed checks.x86_64-linux.bcachefs 21m 39s
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 906.81 seconds (timeout=900.0)
cleanup
kill QemuMachine (pid 117)
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/73e728ddb6b7a12d18808f510813a13ee1fe4cce?narHash=sha256-V6OBJccNKBo/ktknxlJXZChPoI0NE2lembArBO3CE9k%3D»/pkgs/stdenv/generic/make-derivation.nix:651:11

       … while evaluating attribute 'args' of derivation 'nixos-disko-images'
         at «github:NixOS/nixpkgs/73e728ddb6b7a12d18808f510813a13ee1fe4cce?narHash=sha256-V6OBJccNKBo/ktknxlJXZChPoI0NE2lembArBO3CE9k%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/sii8j2xhns057iw31hj6nlzfp13ga247-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 ⚠ 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
3s
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
0s
succeeded checks.x86_64-linux.disko-install
  • stdenv.isDarwin is deprecated, use stdenv.hostPlatform.isDarwin instead
29m 39s
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
2s
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
5m 14s
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
5m 16s
succeeded checks.x86_64-linux.mdadm-btrfs-wipe
  • mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
4m 53s
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
3m 29s
succeeded checks.aarch64-darwin.checkJqSyntax 3s
succeeded checks.aarch64-darwin.disko-doc 26s
succeeded checks.aarch64-darwin.treefmt 16s
succeeded checks.aarch64-linux.checkJqSyntax 1s
succeeded checks.aarch64-linux.disko-doc 10s
succeeded checks.aarch64-linux.treefmt 4s
succeeded checks.x86_64-linux.boot-raid1 6m 22s
succeeded checks.x86_64-linux.btrfs-only-root-subvolume 5m 49s
succeeded checks.x86_64-linux.btrfs-subvolumes 5m 49s
succeeded checks.x86_64-linux.checkJqSyntax 5s
succeeded checks.x86_64-linux.cli 6m 28s
succeeded checks.x86_64-linux.complex 6m 29s
succeeded checks.x86_64-linux.disko-doc 1m 41s
succeeded checks.x86_64-linux.f2fs 5m 40s
succeeded checks.x86_64-linux.gpt-bios-compat 5m 38s
succeeded checks.x86_64-linux.gpt-name-with-special-chars 5m 43s
succeeded checks.x86_64-linux.gpt-unformatted 5m 31s
succeeded checks.x86_64-linux.hybrid 5m 32s
succeeded checks.x86_64-linux.hybrid-mbr 5m 36s
succeeded checks.x86_64-linux.hybrid-tmpfs-on-root 5m 29s
succeeded checks.x86_64-linux.long-device-name 5m 18s
succeeded checks.x86_64-linux.luks-btrfs-raid 6m 11s
succeeded checks.x86_64-linux.luks-btrfs-subvolumes 6m 11s
succeeded checks.x86_64-linux.luks-fido2 5m 39s
succeeded checks.x86_64-linux.luks-interactive-login 5m 54s
succeeded checks.x86_64-linux.luks-lvm 6m 8s
succeeded checks.x86_64-linux.luks-on-mdadm 5m 51s
succeeded checks.x86_64-linux.luks-password-mismatch 5m 5s
succeeded checks.x86_64-linux.lvm-raid 5m 12s
succeeded checks.x86_64-linux.lvm-sizes-sort 5m 6s
succeeded checks.x86_64-linux.lvm-thin 5m 4s
succeeded checks.x86_64-linux.mdadm 5m 17s
succeeded checks.x86_64-linux.mdadm-raid0 5m 14s
succeeded checks.x86_64-linux.mdadm-raid5-args 5m 15s
succeeded checks.x86_64-linux.module 5m 40s
succeeded checks.x86_64-linux.multi-device-no-deps 4m 37s
succeeded checks.x86_64-linux.negative-size 4m 26s
succeeded checks.x86_64-linux.non-root-zfs 5m 11s
succeeded checks.x86_64-linux.simple-efi 4m 44s
succeeded checks.x86_64-linux.swap 4m 40s
succeeded checks.x86_64-linux.tmpfs 4m 37s
succeeded checks.x86_64-linux.treefmt 1m 17s
succeeded checks.x86_64-linux.with-lib 4m 34s
succeeded checks.x86_64-linux.xfs 4m 37s
succeeded checks.x86_64-linux.zfs 4m 45s
succeeded checks.x86_64-linux.zfs-encrypted-root 4m 36s
succeeded checks.x86_64-linux.zfs-over-legacy 4m 38s
succeeded checks.x86_64-linux.zfs-with-vdevs 6m 12s