about summary refs log tree commit diff
path: root/pkgs/test
AgeCommit message (Collapse)AuthorFilesLines
2021-05-17Merge remote-tracking branch 'origin/master' into staging-nextJonathan Ringer1-0/+2
Conflicts: pkgs/development/tools/rust/cargo-cache/default.nix pkgs/development/tools/rust/cargo-embed/default.nix pkgs/development/tools/rust/cargo-flash/default.nix pkgs/servers/nosql/influxdb2/default.nix
2021-05-15writeDirectReferencesToFile: initRobert Hensing1-0/+2
2021-05-08treewide: fix cargoSha256/cargoHashDaniël de Kok1-1/+1
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which cargo vendor erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are potentially broken. This change updates cargoSha256/cargoHash tree-wide. Fixes #121994.
2021-05-07Merge branch 'master' into haskell-updatesMalte Brandy1-56/+57
2021-05-02tests.texlive.dvipng: apply recurseIntoAttrsDmitry Kalinkin1-56/+57
2021-05-02tests.haskell-setBuildTarget: inline haskell package def to avoid IFD(cdep)illabout1-5/+17
2021-05-02Add haskell.lib.setBuiltTarget, and support non library compiling of a ↵Isaac Shapira6-0/+53
single target
2021-05-01tests.haskell.shellFor: use writeText instead of toFilesternenseemann1-2/+2
2021-05-01tests.haskell.shellFor: replace database-id-class with linearsternenseemann1-4/+4
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.
2021-05-01tests.haskell*: move into tests.haskell setsternenseemann4-2/+7
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.
2021-04-21tests.vim: init (moved from vim-utils.nix) (#119467)Matthieu Coudron2-0/+74
* 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.vim
2021-04-18cudatoolkit-{9,9_0,9_1,9_2}: removeDaniël de Kok2-10/+0
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.
2021-03-18texlive.bin.dvipng: refactor gs hardcoding, add a test for itDmitry Kalinkin1-2/+43
2021-03-17maintainers-list: obsidian-systems-maintenanceJohn Ericson2-2/+2
Fix mispelling. That word always breaks me...
2021-03-17tests.cude.cuda-library-samples.cutensor: init at same version as othersJohn Ericson2-0/+26
2021-03-17tests.cude.cuda-library-samples.{cublas,cusolver}: init at masterJohn Ericson3-0/+96
Well, strictly speaking, master + https://github.com/NVIDIA/CUDALibrarySamples/pull/29
2021-03-17tests.cuda.cuda-sample_*: Init at supported CUDA toolkit versionsJohn Ericson4-0/+121
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.
2021-02-09tests.patch-shebangs: add case for ignoring store pathsAndrew Childs1-16/+60
2021-01-25treewide: remove stdenv where not neededPavol Rusnak2-2/+2
2021-01-24treewide: stdenv.lib -> libPavol Rusnak6-22/+22
2020-12-27bintools-wrapper: skip dynamic linker for static binariesJörg Thalheim1-4/+19
2020-12-21Revert "bintools-wrapper: skip dynamic linker for static binaries"Vladimír Čunát1-19/+4
This reverts commit ccfd26ef14ea213320f0b49db3fb347785b38f06. These toolchain changes are too problematic, so reverting for now; see https://github.com/NixOS/nixpkgs/pull/107086#issuecomment-749196366
2020-12-20Merge master into staging-nextgithub-actions[bot]1-0/+1
2020-12-19buildRustCrateTests: Move to tests.buildRustCrateJohn Ericson1-0/+1
I think it is preferable to separate the tests from the "real" packages.
2020-12-14tests.cc-wrapper: disable static compilation macOSJörg Thalheim1-8/+11
macOS does not support this
2020-12-14bintools-wrapper: skip dynamic linker for static binariesJörg Thalheim1-4/+16
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.
2020-11-28rust: Clean up target configs and test some moreJohn Ericson1-23/+37
See the new docs for details. The difference is vis-a-vis older versions of this PR, not master.
2020-11-28Merge remote-tracking branch 'upstream/master' into aj-rust-custom-targetJohn Ericson3-0/+145
2020-11-13haskell: Add documentationTarball to libJoe Hermaszewski2-0/+18
2020-10-26Recover the complicated situation after my bad mergeVladimír Čunát2-0/+127
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
2020-10-25Revert "Merge #101508: libraw: 0.20.0 -> 0.20.2"Vladimír Čunát2-127/+0
I'm sorry; I didn't notice it contained staging commits. This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
2020-10-17fix whitespaceAaron Janse1-1/+1
2020-10-17remove trailing periodAaron Janse1-1/+1
2020-10-17add `meta` to rust-sysroot testAaron Janse1-1/+6
2020-10-17add testAaron Janse2-0/+43
2020-10-11Merge branch 'staging-next' into stagingJan Tojnar2-0/+68
2020-10-08installShellFiles: Add test suiteLily Ballard2-0/+127
2020-10-06tests.texlive: initDmitry Kalinkin2-0/+68
2020-09-25tests.haskell-shellFor: get compiling again(cdep)illabout1-7/+16
2020-07-23stdenv: make -nostdinc work as intendedJörg Thalheim3-0/+17
Right now we add glibc to search path also -nostdinc was provided, which breaks projects providing their own gcc.
2020-05-22Merge pull request #84032 from teto/fix_kernel_mergeFlorian Klink1-32/+58
Fix kernel configuration merge
2020-05-16pkg-config-wrapper: InitJohn Ericson1-0/+14
This fixes longstanding build issues
2020-05-16cross/tests: Use `crossPkgs.runCommand` so we have `strictDeps`John Ericson1-1/+1
2020-04-01kernel: fix config generationMatthieu Coudron1-32/+58
Addresses https://github.com/NixOS/nixpkgs/issues/71803: Kernel options are not merged as described, especially the "optional" aspects. The error silences legitimate warnings.
2020-02-09tests.nixos-functions: port test to pythonworldofpeace1-1/+1
2020-01-30llvm_4: removeLuka Blaskovic1-2/+0
2020-01-30llvm_39: removeLuka Blaskovic1-2/+0
2020-01-17Merge remote-tracking branch 'obsidiansystems/work-on-multi-shellFor'Matthew Bauer2-0/+26
2020-01-17shellFor: Refactor for consistency and crossJacquin Mininger2-0/+26
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.
2019-09-19tests.cc-wrapper-{clang,libcxx}-{8,9}: add stdenv tests for LLVM 8, 9Will Dietz1-0/+4
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-20 17:47:39 +0000