Florian Friesdorf <[email protected]> writes: > Eelco Dolstra <[email protected]> writes: >> On 25/06/14 13:34, Florian Friesdorf wrote: >>> I'd like soonish to push and include tests for python in master. Do you >>> see problems with the way I am doing this? >> >> Are these actually NixOS tests? Seems to me that Python tests are more >> something >> to be done in Nixpkgs proper (or maybe in a separate jobset for Python >> tests). >> We don't currently have a tests.* set in the Nixpkgs release.nix, but it >> would >> be good to have one. > > They test the usage and interaction of python packages installed into a > nix profile. > > Currently, they use the system profile and are therefore NixOS-specific, > but could be fixed easily to use any profile. > > Further, it would be enough to have a profile and an empty directory to > run the tests with, the nixos test isolation with qemu seems to be > overkill.
It would be enough and even more comfortable if the test script would just be a (ba)sh script run with -e. I can imagine how to do this based on mkDerivation, but fail yet to see how to create something similar to a profile with the test dependencies installed. Currently, I have tests failing when run with packages from the system profile, but they succeed when reproduced with a "normal" profile. So it seems important how the profile is created. > Does that qualify for a python-tests jobset within nixpkgs? > Where to go from here? -- Florian Friesdorf <[email protected]> GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083 Jabber/XMPP: [email protected] IRC: chaoflow on freenode,ircnet,blafasel,OFTC
pgpWCwFIIzAAr.pgp
Description: PGP signature
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
