--- expected.txt	2026-10-18 12:39:31.344225628 +0000
+++ /nix/store/09m161kzvmsfkiwqnzmnbq0kjamxk7fp-test-drv-canary-actual	1970-01-01 00:00:01.000000000 +0000
@@ -1,4 +1,4 @@
 testify-basic /nix/store/mlfy1sxk8vpwyslgm5h5h6jfiw2ma3g7-testify-basic-0.0.1.drv
 xtest-local-dep /nix/store/dph6225i6rraxzax1q61sg959j3jnwg2-xtest-local-dep-0.0.1.drv
-cgo-internal-test /nix/store/wc9q8z0vzy7kiagvjn57n31xi17afxqa-cgo-internal-test-0.0.1.drv
+cgo-internal-test /nix/store/vrd59l1h1y866ycq9dqil96v18ljlf19-cgo-internal-test-0.0.1.drv
 torture-app-full /nix/store/kcrqqm4dmz6wbm4kfyf3isglaw12wmb6-torture-app-full-0.0.1.drv

FAIL: .drv paths changed.

If the change is meant to leave derivations alone (a refactor of
nix/dag/*.nix or nix/helpers.nix, a plugin change that returns the
same graph), this is a regression.

If it is meant to move them (the nixpkgs flake input, nix/dag/hooks/,
nix/stdlib.nix, a fixture, what the plugin returns, new builder
behaviour), regenerate and commit the result with the change:
  ./scripts/update-drv-canary.sh
Without an x86_64-linux builder, the + lines above are the new
contents of expected.txt.