New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Staging next #104781
Staging next #104781
Conversation
This adds -frandom-seed to each compiler invocation in stdenv. The object here is to make the compierl invocations produce the same output every time they are called (for the same derivation). When the -frandom-seed option is not set the compiler will use a combination of random numbers (in GCC's case from /dev/urandom) and the durrent time to produce a "random" input per file. This can (among other things) lead to different ordering of symbols in the produced object files. For reason of reproducibility we prefer having the same derivation produce the exact same outputs. This is not a silver bullet but one way to tame the compiler.
Sensitive to exact parser output
This reverts commit 0fc5e60. For some reason the v1.0.3 PyPI tarball ships with tests that expect pytest-testmon master instead of the v1.0.3 code (tarpas/pytest-testmon#158), causing these tests to fail against 1.0.3 itself.
stdenv: introduce -frandom-seed
linuxHeaders: 5.5 -> 5.9.8
See https://www.redhat.com/sysadmin/fedora-31-control-group-v2 for details on why this is desirable, and how it impacts containers. Users that need to keep using the old cgroup hierarchy can re-enable it by setting `systemd.unifiedCgroupHierarchy` to `false`. Well-known candidates not supporting that hierarchy, like docker and hidepid=… will disable it automatically. Fixes #73800
This gets automatically disabled by docker if the docker backend is used, but the bundled containerd also doesn't seem to support cgroupsv2, so disable it explicitly here, too.
For now, testing IO Accounting is skipped, as it seems to be either broken, or hard to reproduce in a VM.
Please do not use tarballs.nixos.org in src URLs. tarballs.nixos.org is a cache, not an authority. This patch differs from the one in tarballs.nixos.org only in source code comments.
Hack until we fix PYTHONPATH.
I think the sysconfigdata changes are breaking python37Packages.bootstrapped-pip - hydra log:
|
Sigh. This was the issue spidermonkey_78 had before my fix. That got fixed by using a symlink, and now this one complains with a symlink. OK, next patch, a copy instead. Yet another stdenv rebuild... Also just now aborted all builds on staging-next. |
…ling extension modules""" This still does not function without issues. E.g., bootstrapped-pip fails with Python 3.6 and 3.7 as well as 3.8 on 32-bit. Because this is a stdenv-rebuild it needs to be tested significantly better This reverts commit 6100bc2.
Reverted the Python cross commit again in 0a12b8a. |
Python namespace hook is causing trouble @jonringer
|
Ah, I originally, had a |
fixed:
building ceph now, but it should work... takes a while since ceph has ~2000 build dependencies
ceph builds as well now:
|
Motivation for this change
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
With cross-compilation of Python extension modules.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)