Commit Graph

166477 Commits

Author SHA1 Message Date
Samuel Dionne-Riel
b28b37eb00 tests: Wait for shell for twice as long (10m)
See #49441 for an earlier attempt, which was subsequently reverted. I am
assuming that doubling the time will be sufficient if the machine is
overloaded since so many of the tests already pass at 5 minutes, while
still not holding back failures for needlessly long.
2019-01-11 22:40:19 -05:00
Samuel Dionne-Riel
5d93e2c01c test-driver: Logs time taken for nests 2019-01-11 22:36:31 -05:00
Samuel Dionne-Riel
1fe0018df8 test-driver: Adds time it took to connect to guest in logs
This will make it possible to track whether the time is generous or not
when ran on hydra.
2019-01-11 22:36:31 -05:00
Dmitry Kalinkin
73625f2522 root5: mark as broken on Linux 2019-01-11 20:45:37 -05:00
Dmitry Kalinkin
0c9335fb1c root, root5: fix build on darwin 2019-01-11 20:45:37 -05:00
Edmund Wu
6b80db3f5f
vscode: 1.30.1 -> 1.30.2 2019-01-11 20:02:00 -05:00
Mario Rodas
93369a1b34
pythonPackages.pytest-rerunfailures: 4.2 -> 6.0 2019-01-11 19:39:01 -05:00
Austin Seipp
61e57a827b icestorm: enableParallelBuilding = true
With the previous PyPy3 change, this reduces the compile time from
~1m30s to roughly 36s (compared to the original, serial, Python 3 build
time of 2:30s).

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-01-11 18:03:35 -06:00
Austin Seipp
18839e1cc1 icestorm: improve x86 build/runtime perf with pypy
PyPy3 offers tremendous speedups for IceStorm tools written in Python,
including tools used at compile-time to generate the chip databases, and
runtime tools distributed to users, such as icebox_vlog.

For example, on my ThreadRipper 1950X, build times for IceStorm
consistently go from 2m30s -> 1m30s with this change, a 40% improvement,
simply due to improvements in raw CPU efficiency. (This is also worsened
by the fact the build is currently serial, but that can easily be fixed
anyway.)

On top of that, tools distributed to users are also now run using PyPy.
Utilities such as icebox_vlog are useful for post-bitstream testing, for
instance, and also are improved due to improved CPU efficiency as well.
For example, when "decompiling" an ICE40 bitstream for HX8K devices,
containing a synthesized copy of PicoRV32 (from the NextPNR demos), the
runtime of icebox_vlog is cut from 25 seconds to 9 seconds consistently
with this change alone.

Normally, picking a Python interpreter outright for Python-based code is
a "bad idea", but in the case of IceStorm it should be perfectly safe,
and an excellent improvement for users. There are a few reasons for
this:

  - IceStorm uses pure Python 3 and nothing else. There are no
requirements for any 3rd party packages, which might cause annoying
incompatibilities, and PyPy has historically shown very strong core
Python compatibility.

  - IceStorm is NOT a set of Python libraries, it is a set of tools,
some of which, coincidentally, are written in Python. It is (normally)
bad form to fix libraries to certain interpreters versions if the reason
strictly isn't "it doesn't work/isn't compatible". That is not the case
here. These tools may later be used by other programs, such as NextPNR,
but the Python interpreter is ultimately not that important in quesion
for the user. In this sense, there is almost no downside to picking
PyPy explicitly if it offers far better performance.

(Point 2 is not actually strictly true; there are some distributed .py
files that you can import from but they are basically just static
classes that are imported by tools like nextpnr; this is expected.)

Because of this, users should see very little change except better
performance for IceStorm tools on their machines.

Note that PyPy is not supported on aarch64 -- this only applies to
x86_64 machines.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-01-11 18:03:35 -06:00
Andy Chun @noneucat
3bdcbd8cb9 polar-bookshelf: 1.7.0 -> 1.8.0 2019-01-11 15:58:01 -08:00
worldofpeace
9ccd6471b1
Merge pull request #53602 from ivan/wine-4.0-rc5
wine{Unstable,Staging}: 4.0-rc2 -> 4.0-rc5
2019-01-11 18:06:10 -05:00
R. RyanTM
a8518f976c yarn: 1.12.3 -> 1.13.0
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/yarn/versions
2019-01-12 00:00:57 +02:00
worldofpeace
70013f236b
Merge pull request #51236 from fgaz/cht.sh/init
cht-sh: init at unstable-2018-11-02
2019-01-11 15:19:18 -05:00
Vladimír Čunát
414e66f222
boehmgc: avoid mass rebuild due to the parent commit 2019-01-11 20:12:56 +01:00
Dmitry Kalinkin
ac7f4c0478
boehmgc: fix patch url
Fixes: 587467a18e ('github-gentoo-compromized_can...')
Closes: #53809
2019-01-11 13:20:05 -05:00
Silvan Mosberger
084e008a2a
Merge pull request #53743 from baracoder/add-nvidia-maintainer
linuxPackages.nvidia_x11*: Add maintainer: baracoder
2019-01-11 19:09:40 +01:00
Vincent Laporte
10fa10731e coqPackages.category-theory: bound build parallelism 2019-01-11 17:24:45 +00:00
Joachim F
8ffae68b22
Merge pull request #53806 from pbogdan/krb-test-eval
nixos/tests/kerberos: fix evaluation
2019-01-11 17:09:38 +00:00
Yegor Timoshenko
bb1cb2a332
ghc844: update hash for d8495549ba9d194815c2d0eaee6797fc7c00756a patch 2019-01-11 20:06:22 +03:00
Robert Schütz
b720ecb9ee matrix-synapse: use python3 2019-01-11 16:36:28 +01:00
nyanloutre
bc561526d1 matrix-synapse: 0.34.0.1 -> 0.34.1.1
Also correctly run tests.
2019-01-11 16:36:27 +01:00
nyanloutre
06c08984ae pythonPackages.pysaml2: 3.0.2 -> 4.6.5
Also run tests and hardcode path to xmlsec1.
2019-01-11 16:36:27 +01:00
Michael Raskin
eb5d51d4cf clasp-common-lisp: update/fix build, 2018-11-28 prerelease (towards 0.9) 2019-01-11 16:29:29 +01:00
Joachim F
11cd6aeb0c
Merge pull request #53802 from delroth/kernel-randstruct
Use a deterministic seed for kernel RANDSTRUCT, and re-enable in hardened kernels
2019-01-11 14:49:33 +00:00
Eelco Dolstra
c1a13108e2
nix: Add editline dependency
Also fix incorrect hash for nixUnstable.
2019-01-11 15:05:17 +01:00
Eelco Dolstra
ac97ba25ae
Revert "libgit2: 0.26.6 → 0.27.7"
This reverts commit cc50638176 because
it breaks cargo (again, see fca4fbeba9):

  $ cargo build
      Updating crates.io index
  Segmentation fault
2019-01-11 14:58:45 +01:00
yochai
10b50b661b culmus: add .otf, .pfa and .afm files (#53638)
restructure into stdenv.mkDerivation. This resolves the problem of changing hashes.
2019-01-11 13:57:28 +01:00
Jörg Thalheim
15ec5d03e6
Merge pull request #52563 from vdemeester/52469-containerd-to-buildgopackage
containerd: migrate to using buildGoPackage
2019-01-11 12:29:35 +00:00
Jörg Thalheim
f3cb8cedef
Merge pull request #53744 from prusnak/gcc-arm-embedded-8
gcc-arm-embedded: 7-2018-q2-update -> 8-2018-q4-major
2019-01-11 12:26:13 +00:00
Jörg Thalheim
566cc6bf20
Merge pull request #52572 from vdemeester/52469-openshift-to-buildgopackage
openshift: migrate to using buildGoPackage
2019-01-11 12:22:53 +00:00
Jörg Thalheim
831ffbdc96
Merge pull request #53737 from dpetranek/update-leiningen
leiningen: 2.8.1 -> 2.8.3
2019-01-11 12:06:36 +00:00
Jörg Thalheim
efe523725e
Merge pull request #53718 from jlesquembre/clojure
clojure: 1.10.0.403 -> 1.10.0.411
2019-01-11 12:05:09 +00:00
Robert Schütz
3027e4b736 python.pkgs.mt-940: 4.12.2 -> 4.13.0 2019-01-11 12:53:27 +01:00
Jörg Thalheim
8476d03bb7
Merge pull request #53794 from thefloweringash/rubocop-0.62.0
rubocop: 0.59.1 -> 0.62.0
2019-01-11 11:53:06 +00:00
Eelco Dolstra
94ea1c2d83
nix: 2.1.3 -> 2.2 2019-01-11 12:47:06 +01:00
Jörg Thalheim
b4df112941
Merge pull request #53780 from OPNA2608/obs-scripting
obs-studio: add new optional dependencies
2019-01-11 11:43:27 +00:00
Jörg Thalheim
e40bfa4d85
nixos-rebuild: allow to override builders
Since nix 2.0 the no-build-hook option was replaced by the builders options
that allows to override remote builders ad-hoc.
Since it is useful to disable remote builders updating nixos without network,
this commit reintroduces the option.
2019-01-11 11:40:25 +00:00
Jörg Thalheim
ce9bc1ed81
Merge pull request #53722 from Ma27/fix-python37-on-termbox
termbox: fix build
2019-01-11 11:38:48 +00:00
Pierre Bourdon
b26c824da3
Revert "Revert "Revert "linux-hardened: Disable GCC_PLUGIN_RANDSTRUCT"""
The issue with out-of-tree modules has been addressed and the feature
should now be good to re-enable again.

This reverts commit 865f7a14b4.
2019-01-11 12:35:16 +01:00
Pierre Bourdon
1b9bf8fa75
kernel: make the RANDSTRUCT seed deterministic 2019-01-11 12:35:16 +01:00
Robert Schütz
e9b34b1bfa
pythonPackages.nipype: 1.1.5 -> 1.1.7 (#53254)
* pythonPackages.nipype: 1.1.5 -> 1.1.7

Fix build by dropping a patch for an issue that is already fixed.
See: https://github.com/nipy/nipype/pull/2701

Also had to disable tests.
See: https://github.com/nipy/nipype/issues/2839

* pythonPackages.xvfbwrapper: disable tests

See: https://github.com/cgoldberg/xvfbwrapper/issues/30
2019-01-11 12:28:55 +01:00
Michael Weiss
9b17ee61b8
nvme-cli: 1.6 -> 1.7 2019-01-11 12:23:49 +01:00
Michael Raskin
0feb54c9ae gst_all_1.gst-editing-services: fix build 2019-01-11 11:46:23 +01:00
Michael Raskin
3bd38b0daa lighttpd: fix tests on Linux
The tests were enabled in #53488 and succeeded on Darwin; on Linux they
still failed because of empty hostname inside the sandbox (we have no
UTS-namespace hostname and I think no /etc/hosts). Nix on Darwin lacks
powerful enough sandboxing, so there were no problems on Darwin.

Patching the tests to fallback to "127.0.0.1" if hostname of the
localhost cannot be retrieved matches the behaviour of lighttpd itself
and allows the tests to pass.

Not sure if having no hostname in the test environment is a bit too
weird for the upstream to care.
2019-01-11 11:46:23 +01:00
Herman Fries
ca1f092fe9 linuxPackages.nvidia_x11*: Add maintainer: baracoder
I bought some recent nVidia hardware, so I am stuck with it for a couple
of years and because of this, I have an interest in a working nVidia driver.
2019-01-11 11:36:34 +01:00
Jörg Thalheim
5ef8b40d4d
sysdig: enable 4.20 2019-01-11 10:34:34 +00:00
Francesco Gazzetta
9c3cb094ce cht-sh: init at unstable-2018-11-02 2019-01-11 10:42:37 +01:00
markuskowa
e5c07bde10
Merge pull request #53731 from tadeokondrak/update-neofetch
neofetch: 5.0.0 -> 6.0.0
2019-01-11 10:25:24 +01:00
Franz Pletz
9ea5b2c052
nginxMainline: 1.15.7 -> 1.15.8 2019-01-11 07:55:25 +01:00
Franz Pletz
3db072d823
prometheus-node-exporter: now works with recent go 2019-01-11 07:55:25 +01:00