diff options
| author | Tucker Shea <tucker@tuckershea.com> | 2025-12-22 10:16:03 -0500 |
|---|---|---|
| committer | Tucker Shea <tucker@tuckershea.com> | 2025-12-22 10:26:13 -0500 |
| commit | efa95b1907257053f8b7ea1a36f6ac275c4d56d3 (patch) | |
| tree | 77084ef20711fc8a76a61d7ac56c161bab9a2635 /pkgs/development/python-modules/python-sql | |
| parent | ea3f93e4e3fe2c104f783cb582e4fe19a977f7f8 (diff) | |
python313Packages.celery: skip tests that check group
Fixes builds on NixOS 25.11/unstable on aarch64-linux
and x86_64-linux. Resolves #471417.
Celery attempts to prevent running as root when
the pickle format is enabled, as pickles allow
arbitrary code execution on load. If it cannot
get information about the current user or group,
it assumes that it is running as root.
This is expected behavior.
https://github.com/celery/celery/blame/0527296acb1f1790788301d4395ba6d5ce2a9704/celery/platforms.py#L807-L814
On some machines, it cannot obtain this information
in the build sandbox, and the build fails. The two
latest 25.11 tags fail to build on two of my machines
(25.11.20250627.30e2e28 aarch64-linux and
25.11.20250627.30e2e28 x86_64-linux)
as well as my CI:
nix build nixpkgs/c8cfcd6#python313Packages.celery --rebuild
nix build nixpkgs/c6f52eb#python313Packages.celery --rebuild
A reasonable alternative would be to set
C_FORCE_ROOT in the check environment. I choose to
instead disable the failing tests based on precedent
(previous tests that fail similarly are disabled)
and to avoid complications if a test depends on the
absence of C_FORCE_ROOT now or in the future.
Diffstat (limited to 'pkgs/development/python-modules/python-sql')
0 files changed, 0 insertions, 0 deletions