Matthieu Coudron

> In rocks (the rust package), we have a ROCKS_SKIP_IMPURE_TESTS env variable that we set to true in the nix build environment. good to know ! > Perhaps the simplest...

I can run the tests successfully if I remove 6 out of the 7 files in spec/operations, just keeping parser_spec.lua ``` rm spec/operations/install_update_spec.lua spec/operations/sync_spec.lua \ spec/operations/helpers_spec.lua spec/adapter_spec.lua \ spec/operations/pin_spec.lua spec/operations/bulk_install_spec.lua...

btw do we run the busted tests in CI?

done in linked PR.

I dont think it warrants its own command. Ideally `dev` would be a conscious choice rather than the current way of dealing with missing rockspecs. If one wants to switch...

So basically the tests fail because `mkdir` is called in fast context by adapter.init(). I've tried to convert the async adapter.init into a sync one replacing everything `nio.X` by `vim.X`...

the async problem should have been solved in https://github.com/lumen-oss/rocks.nvim/pull/686, which makes this PR simpler, aka just tagging the tests such that we can select tests that run in the nix...

if there is a rebase I can help testdrive this as well. Like the previous commenter, heavy user of nix flakes and git worktrees.

I've just noticed that nixpkgs does: ``` wrapProgram $out/bin/fortune-kind \ --prefix FORTUNE_DIR : "$out/fortunes" ``` but when I tried ``` ➜ export FORTUNE_DIR=/home/teto/home/fortunes nixpkgs on  nixos-unstable ➜ fortune-kind No...

a possibly similar usecase: in my current config, my nixosConfigurations exist once with `withSecrets=true` and once with `withSecrets=false`. It lets me boostrap my config without having all my secrets available...