Skip or fix tests in nix-like sanboxes

[layus]

Some hnix-store-remote tests do not work in sandboxes because of reasons. I think the use of namespaces, or possibly opening a socket is a problem.

We should make these tests sandbox-friendly, or skip them so as to make the test pass in this setup.

Also related to a proper hnix-store ci :-)

[sorki]

I've added io-testsuite flag recently (https://github.com/haskell-nix/hnix-store/blob/master/hnix-store-remote/hnix-store-remote.cabal#L16) to remedy this but testing the build it looks like it's ignored. Not sure why.

[layus]

Well, it is just explicitly turned on in

hnix-store/overlay.nix

Line 5 in 04444ce

helf.callCabal2nixWithOptions "hnix-store-remote" ./hnix-store-remote "-fio-testsuite" {};

. We could change that in hnix. Just override the set of flags.

[sorki]

Ah thanks. I didn't notice you use overlay from here. dontCheck is fine for now or I can disable the flag in the overlay and just enable it for shell / local build.

Like this will go away with the nixpkgs PR fixing cryptohash-sha512 and being able to use both from nixpkgs. Trying to figure out what's going on I've manage to update both in nixpkgs and noticed missing extra files for -core.

Alternatively we can enable tests in hnix, the only requirement is nix (nix-daemon) being present so harness can setup temporary environment. Will take a look.

[layus]

Found a workaround for now https://github.com/haskell-nix/hnix/pull/554/files#diff-245563af9e34754739b12b294f3324c1d42c116ace7ce8735e21dfbc82d8e064R232-R235

[Anton-Latukha]

Topic was fixed by sorki in #59 and already released in 0.3 and it is already used in the CI.
All discussed in the topic currently is done.

Feel free to reopen.

Probably what you discuss - is that HNix may use the dev state of the HNix-Store for Nix build. For Cabal build may also.
But CI builds with use of Hackage and the master branches - have different meanings. Hackage/Nixpkgs builds - assure that the project complies to the Hackage/Nixpkgs deps state. In HNix use of master branch of HNix-Store would mean the development state test, and that builds would depend on the state of the HNix-Store.