summaryrefslogtreecommitdiff
path: root/pkgs/test (follow)
Commit message (Expand)AuthorAgeFilesLines
* writeDirectReferencesToFile: initRobert Hensing2021-05-151-0/+2
* Merge branch 'master' into haskell-updatesMalte Brandy2021-05-071-56/+57
|\
| * tests.texlive.dvipng: apply recurseIntoAttrsDmitry Kalinkin2021-05-021-56/+57
* | tests.haskell-setBuildTarget: inline haskell package def to avoid IFD(cdep)illabout2021-05-021-5/+17
* | Add haskell.lib.setBuiltTarget, and support non library compiling of a single...Isaac Shapira2021-05-026-0/+53
* | tests.haskell.shellFor: use writeText instead of toFilesternenseemann2021-05-011-2/+2
* | tests.haskell.shellFor: replace database-id-class with linear•••Contrary to database-id-class, linear is part of stackage and actively maintained, so the test is less likely to fail due to version constraint issues as it is currently. sternenseemann2021-05-011-4/+4
* | tests.haskell*: move into tests.haskell set•••This will make it easier to add all haskell related tests to the haskell hydra jobset without updating a list of tests in two places. sternenseemann2021-05-014-2/+7
|/
* tests.vim: init (moved from vim-utils.nix) (#119467)•••* tests.vim: init (moved from vim-utils.nix) Moved tests from pkgs/misc/vim-plugins/vim-utils.nix to pkgs/test/vim. Also reduced the amount of generated config: - Make it possible to have an empty config when configured adequately - removed default vim config when using native packages, it could be source of bugs see linked issues (syntax on overrides vim highlights) Things to watch out for: - if you set configure.beforePlugins yourself, you will need to add set nocompatible too not to lose it - filetype indent plugin on | syn on is not enabled anymore by default for the vim-plug installer: I dont think we should override vim defualts, at least not here since it is shared with neovim. Also sometimes it's enabled before plugins (pathogen etc,) which is not consistent. you can run the tests via $ nix-build -A tests.vimMatthieu Coudron2021-04-212-0/+74
* cudatoolkit-{9,9_0,9_1,9_2}: remove•••Remove old CUDA toolkits (and corresponding CuDNN versions). - Not supported by upstream anymore. - We do not use them in nixpkgs. - We do not test or actively maintain them. - Anything but ancient GPUs is supported by newer toolkits. Fixes #107131. Daniël de Kok2021-04-182-10/+0
* texlive.bin.dvipng: refactor gs hardcoding, add a test for itDmitry Kalinkin2021-03-181-2/+43
* maintainers-list: obsidian-systems-maintenance•••Fix mispelling. That word always breaks me... John Ericson2021-03-172-2/+2
* tests.cude.cuda-library-samples.cutensor: init at same version as othersJohn Ericson2021-03-172-0/+26
* tests.cude.cuda-library-samples.{cublas,cusolver}: init at master•••Well, strictly speaking, master + https://github.com/NVIDIA/CUDALibrarySamples/pull/29 John Ericson2021-03-173-0/+96
* tests.cuda.cuda-sample_*: Init at supported CUDA toolkit versions•••Since CUDA is unfree, we won't actually use this when testing Nixpkgs officially. But I want to include this as they are useful for users of Nixpkgs trying to set up / debug a CUDA environment. John Ericson2021-03-174-0/+121
* tests.patch-shebangs: add case for ignoring store pathsAndrew Childs2021-02-091-16/+60
* treewide: remove stdenv where not neededPavol Rusnak2021-01-252-2/+2
* treewide: stdenv.lib -> libPavol Rusnak2021-01-246-22/+22
* bintools-wrapper: skip dynamic linker for static binariesJörg Thalheim2020-12-271-4/+19
* Revert "bintools-wrapper: skip dynamic linker for static binaries"•••This reverts commit ccfd26ef14ea213320f0b49db3fb347785b38f06. These toolchain changes are too problematic, so reverting for now; see https://github.com/NixOS/nixpkgs/pull/107086#issuecomment-749196366 Vladimír Čunát2020-12-211-19/+4
* Merge master into staging-nextgithub-actions[bot]2020-12-201-0/+1
|\
| * buildRustCrateTests: Move to tests.buildRustCrate•••I think it is preferable to separate the tests from the "real" packages. John Ericson2020-12-191-0/+1
* | tests.cc-wrapper: disable static compilation macOS•••macOS does not support this Jörg Thalheim2020-12-141-8/+11
* | bintools-wrapper: skip dynamic linker for static binaries•••Currently we set dynamic-linker unconditionally. This breaks however some static binaries i.e. rust binaries linked against musl. There is no reason we should set an elf interpreter for static binaries hence this is skipped if `-static` or `-static-pie` is either passed to our cc or ld wrapper. Jörg Thalheim2020-12-141-4/+16
|/
* rust: Clean up target configs and test some more•••See the new docs for details. The difference is vis-a-vis older versions of this PR, not master. John Ericson2020-11-281-23/+37
* Merge remote-tracking branch 'upstream/master' into aj-rust-custom-targetJohn Ericson2020-11-283-0/+145
|\
| * haskell: Add documentationTarball to libJoe Hermaszewski2020-11-132-0/+18
| * Recover the complicated situation after my bad merge•••I made a mistake merge. Reverting it in c778945806b undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range: 4effe769e2b - `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from 4effe769e2) - merging the last unaffected staging-next commit (803ca85c209) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state Vladimír Čunát2020-10-262-0/+127
| * Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"•••I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075. Vladimír Čunát2020-10-252-127/+0
| * Merge branch 'staging-next' into stagingJan Tojnar2020-10-112-0/+68
| |\
| * | installShellFiles: Add test suiteLily Ballard2020-10-082-0/+127
* | | fix whitespaceAaron Janse2020-10-171-1/+1
* | | remove trailing periodAaron Janse2020-10-171-1/+1
* | | add `meta` to rust-sysroot testAaron Janse2020-10-171-1/+6
* | | add testAaron Janse2020-10-172-0/+43
| |/ |/|
* | tests.texlive: initDmitry Kalinkin2020-10-062-0/+68
|/
* tests.haskell-shellFor: get compiling again(cdep)illabout2020-09-251-7/+16
* stdenv: make -nostdinc work as intended•••Right now we add glibc to search path also -nostdinc was provided, which breaks projects providing their own gcc. Jörg Thalheim2020-07-233-0/+17
* Merge pull request #84032 from teto/fix_kernel_merge•••Fix kernel configuration mergeFlorian Klink2020-05-221-31/+57
|\
| * kernel: fix config generation•••Addresses https://github.com/NixOS/nixpkgs/issues/71803: Kernel options are not merged as described, especially the "optional" aspects. The error silences legitimate warnings. Matthieu Coudron2020-04-011-31/+57
* | pkg-config-wrapper: Init•••This fixes longstanding build issues John Ericson2020-05-161-0/+14
* | cross/tests: Use `crossPkgs.runCommand` so we have `strictDeps`John Ericson2020-05-161-1/+1
|/
* tests.nixos-functions: port test to pythonworldofpeace2020-02-091-1/+1
* llvm_4: removeLuka Blaskovic2020-01-301-2/+0
* llvm_39: removeLuka Blaskovic2020-01-301-2/+0
* Merge remote-tracking branch 'obsidiansystems/work-on-multi-shellFor'Matthew Bauer2020-01-172-0/+26
|\
| * shellFor: Refactor for consistency and cross•••This makes it work like work-on-multi from Reflex Platform. In particular, rather than making `.env` from `shellFor`, we make `.env` the primitive, and `shellFor` works by combining together the arguments of all the packages to `generic-builder` and taking the `.env` of the resulting mashup-package. There are 2 benefits of this: 1. The dependency logic is deduplicated. generic builder just concatted lists, whereas all the envs until now would sieve apart haskell and system build inputs. Now, they both decide haskell vs system the same way: according to the argument list and without reflection. Consistency is good, especially because it mean that if the build works, the shell is more likely to work. 2. Cross is handled better. For native builds, because the `ghcWithPackages` calls would shadow, we through both the regular component (lib, exe, test, bench) haskell deps and Setup.hs haskell deps in the same `ghcWithPackages` call. But for cross builds we use `buildPackages.ghcWithPackages` to get the setup deps. This ensures everything works correctly. Jacquin Mininger2020-01-172-0/+26
* | tests.cc-wrapper-{clang,libcxx}-{8,9}: add stdenv tests for LLVM 8, 9Will Dietz2019-09-191-0/+4
|/
* treewide: remove redundant recvolth2019-08-281-1/+1
* treewide: use dontUnpackworldofpeace2019-07-012-4/+4