nixpkgs/pkgs/tools/system/stress-ng/default.nix
2023-06-21 15:11:29 +02:00

75 lines
3.1 KiB
Nix

{ lib, stdenv, fetchFromGitHub
, attr, judy, keyutils, libaio, libapparmor, libbsd, libcap, libgcrypt, lksctp-tools, zlib
}:
stdenv.mkDerivation rec {
pname = "stress-ng";
version = "0.15.10";
src = fetchFromGitHub {
owner = "ColinIanKing";
repo = pname;
rev = "V${version}";
hash = "sha256-JRdqbZAWcPBNspziM/qo2ioIaJOrMgLmx10w7NNaps0=";
};
postPatch = ''
sed -i '/\#include <bsd\/string.h>/i #undef HAVE_STRLCAT\n#undef HAVE_STRLCPY' stress-ng.h
''; # needed because of Darwin patch on libbsd
# All platforms inputs then Linux-only ones
buildInputs = [ judy libbsd libgcrypt zlib ]
++ lib.optionals stdenv.hostPlatform.isLinux [
attr keyutils libaio libapparmor libcap lksctp-tools
];
makeFlags = [
"BINDIR=${placeholder "out"}/bin"
"MANDIR=${placeholder "out"}/share/man/man1"
"JOBDIR=${placeholder "out"}/share/stress-ng/example-jobs"
"BASHDIR=${placeholder "out"}/share/bash-completion/completions"
];
env.NIX_CFLAGS_COMPILE = lib.optionalString stdenv.hostPlatform.isMusl "-D_LINUX_SYSINFO_H=1";
# Won't build on i686 because the binary will be linked again in the
# install phase without checking the dependencies. This will prevent
# triggering the rebuild. Why this only happens on i686 remains a
# mystery, though. :-(
enableParallelBuilding = (!stdenv.isi686);
meta = with lib; {
description = "Stress test a computer system";
longDescription = ''
stress-ng will stress test a computer system in various selectable ways. It
was designed to exercise various physical subsystems of a computer as well as
the various operating system kernel interfaces. Stress-ng features:
* over 210 stress tests
* over 50 CPU specific stress tests that exercise floating point, integer,
bit manipulation and control flow
* over 20 virtual memory stress tests
* portable: builds on Linux, Solaris, *BSD, Minix, Android, MacOS X,
Debian Hurd, Haiku, Windows Subsystem for Linux and SunOs/Dilos with
gcc, clang, tcc and pcc.
stress-ng was originally intended to make a machine work hard and trip hardware
issues such as thermal overruns as well as operating system bugs that only
occur when a system is being thrashed hard. Use stress-ng with caution as some
of the tests can make a system run hot on poorly designed hardware and also can
cause excessive system thrashing which may be difficult to stop.
stress-ng can also measure test throughput rates; this can be useful to observe
performance changes across different operating system releases or types of
hardware. However, it has never been intended to be used as a precise benchmark
test suite, so do NOT use it in this manner.
'';
homepage = "https://github.com/ColinIanKing/stress-ng";
downloadPage = "https://github.com/ColinIanKing/stress-ng/tags";
changelog = "https://github.com/ColinIanKing/stress-ng/raw/V${version}/debian/changelog";
license = licenses.gpl2Plus;
maintainers = with maintainers; [ c0bw3b ];
platforms = platforms.unix;
};
}