From 9b45d8f347efbb4c17d0ace34766725e520b8b9b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gutyina=20Gerg=C5=91?= Date: Sun, 2 Aug 2026 19:24:56 +0200 Subject: [PATCH] test/pnpm: fix fixup-state-db test by storing SQL dump Fixup-state-db is effectively only used in fetchPnpmDeps. We previously included the SQLite database in the FOD, it was first problematic as it produced different hashes on linux and darwin, but SQLite version updates have a higher chance of changing the DB format and break our hashes, that just happened with the 3.53.1 -> 3.53.3 bump. Nowadays fetchPnpmDeps relies on the SQL dump of the database which is more stable, but in the past hashes were broken once. The point is, we no longer rely on the raw DB, but only it's dump, so it's safe to assert for that in this test. --- pkgs/test/pnpm/pnpm-fixup-state-db/default.nix | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pkgs/test/pnpm/pnpm-fixup-state-db/default.nix b/pkgs/test/pnpm/pnpm-fixup-state-db/default.nix index a9f59e3c05ee..ac30f9a392be 100644 --- a/pkgs/test/pnpm/pnpm-fixup-state-db/default.nix +++ b/pkgs/test/pnpm/pnpm-fixup-state-db/default.nix @@ -16,8 +16,8 @@ testers.runCommand { pnpm-fixup-state-db ./store - cp ./store/index.db $out + sqlite3 ./store/index.db .dump > $out ''; - hash = "sha256-P3PDQAziwUxl2pfYV+QyPVwNpq90Jg46bawTvrT0NOQ="; + hash = "sha256-PEzcJgGRo+dK5X9TBcx3A+BOIsvJ7gFmzV8vanTuGCo="; }