nixbot

builds

nix-community/disko build #179 failed

branch master · PR #1273 · commit 23ad3df85b · · took 25m 21s · eval 2m 0s

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 18m 50s
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 914.76 seconds (timeout=900.0)
cleanup
kill QemuMachine (pid 127)
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.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/b6c8664de9b6cc07fe5666a29f91884ba81197c4?narHash=sha256-641r7xrlSOHYoktL9/aArPIYNgZJ9eM5URzSEOtPJDY%3D»/pkgs/stdenv/generic/make-derivation.nix:651:11

       … while evaluating attribute 'args' of derivation 'nixos-disko-images'
         at «github:NixOS/nixpkgs/b6c8664de9b6cc07fe5666a29f91884ba81197c4?narHash=sha256-641r7xrlSOHYoktL9/aArPIYNgZJ9eM5URzSEOtPJDY%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/cz4kshwvyq62f857x0wvydhkqwkzdakl-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
1s
succeeded checks.x86_64-linux.disko-install
  • stdenv.isDarwin is deprecated, use stdenv.hostPlatform.isDarwin instead
24m 30s
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
2m 10s
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 8s
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 3s
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 7s
succeeded checks.aarch64-darwin.checkJqSyntax 3s
succeeded checks.aarch64-darwin.disko-doc 18s
succeeded checks.aarch64-darwin.treefmt 9s
succeeded checks.aarch64-linux.checkJqSyntax 1s
succeeded checks.aarch64-linux.disko-doc 7s
succeeded checks.aarch64-linux.treefmt 3s
succeeded checks.x86_64-linux.boot-raid1 3m 6s
succeeded checks.x86_64-linux.btrfs-only-root-subvolume 2m 26s
succeeded checks.x86_64-linux.btrfs-subvolumes 2m 27s
succeeded checks.x86_64-linux.checkJqSyntax 1s
succeeded checks.x86_64-linux.cli 3m 25s
succeeded checks.x86_64-linux.complex 3m 31s
succeeded checks.x86_64-linux.disko-doc 21s
succeeded checks.x86_64-linux.f2fs 2m 26s
succeeded checks.x86_64-linux.gpt-bios-compat 2m 20s
succeeded checks.x86_64-linux.gpt-name-with-special-chars 2m 26s
succeeded checks.x86_64-linux.gpt-unformatted 2m 12s
succeeded checks.x86_64-linux.hybrid 2m 13s
succeeded checks.x86_64-linux.hybrid-mbr 2m 17s
succeeded checks.x86_64-linux.hybrid-tmpfs-on-root 2m 24s
succeeded checks.x86_64-linux.long-device-name 2m 11s
succeeded checks.x86_64-linux.luks-btrfs-raid 3m 21s
succeeded checks.x86_64-linux.luks-btrfs-subvolumes 3m 8s
succeeded checks.x86_64-linux.luks-fido2 2m 48s
succeeded checks.x86_64-linux.luks-interactive-login 2m 58s
succeeded checks.x86_64-linux.luks-lvm 3m 14s
succeeded checks.x86_64-linux.luks-on-mdadm 3m 5s
succeeded checks.x86_64-linux.luks-password-mismatch 2m 12s
succeeded checks.x86_64-linux.lvm-raid 2m 30s
succeeded checks.x86_64-linux.lvm-sizes-sort 2m 5s
succeeded checks.x86_64-linux.lvm-thin 1m 59s
succeeded checks.x86_64-linux.mdadm 2m 17s
succeeded checks.x86_64-linux.mdadm-raid0 2m 16s
succeeded checks.x86_64-linux.mdadm-raid5-args 2m 12s
succeeded checks.x86_64-linux.module 2m 26s
succeeded checks.x86_64-linux.multi-device-no-deps 1m 1s
succeeded checks.x86_64-linux.negative-size 56s
succeeded checks.x86_64-linux.non-root-zfs 2m 13s
succeeded checks.x86_64-linux.simple-efi 1m 17s
succeeded checks.x86_64-linux.swap 1m 49s
succeeded checks.x86_64-linux.tmpfs 1m 30s
succeeded checks.x86_64-linux.treefmt 12s
succeeded checks.x86_64-linux.with-lib 1m 43s
succeeded checks.x86_64-linux.xfs 1m 33s
succeeded checks.x86_64-linux.zfs 1m 51s
succeeded checks.x86_64-linux.zfs-encrypted-root 1m 34s
succeeded checks.x86_64-linux.zfs-over-legacy 1m 33s
succeeded checks.x86_64-linux.zfs-with-vdevs 3m 13s