dev-build/gyp has quite a number of failing tests right now, but they are nonfatal because there's no "|| die" in the ebuild. Example from arm64: Failed the following 19 tests: (test/assembly/gyptest-assembly.py) make (test/assembly/gyptest-assembly.py) ninja (test/errors/gyptest-errors.py) ninja (test/linux/gyptest-implicit-rpath.py) make (test/linux/gyptest-implicit-rpath.py) ninja (test/linux/gyptest-target-rpath.py) ninja (test/make_global_settings/ar/gyptest-make_global_settings_ar.py) ninja (test/rules/gyptest-all.py) make (test/rules/gyptest-all.py) ninja (test/rules/gyptest-default.py) make (test/rules/gyptest-default.py) ninja (test/variables/commands/gyptest-commands-ignore-env.py) make (test/variables/commands/gyptest-commands-ignore-env.py) ninja (test/variables/commands/gyptest-commands-repeated.py) make (test/variables/commands/gyptest-commands-repeated.py) ninja (test/variables/commands/gyptest-commands.py) make (test/variables/commands/gyptest-commands.py) ninja (test/variables/filelist/gyptest-filelist-golden.py) make (test/variables/filelist/gyptest-filelist-golden.py) ninja Ran 712 tests in 603.091s, 19 failed. >>> Completed testing dev-build/gyp-20200512145953 Reproducible: Always
Created attachment 883877 [details] build.log and emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6cc9b02ac62bfb6d4e83be553e683aaa0a6948e6 commit 6cc9b02ac62bfb6d4e83be553e683aaa0a6948e6 Author: Sam James <sam@gentoo.org> AuthorDate: 2025-03-31 17:19:31 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-03-31 17:32:00 +0000 dev-build/gyp: port to python-single-r1 The package isn't suitable for PEP517, as it installs data files and it simply happens to be written in Python, rather than intending to be imported and so on. Unfortunately, for the remaining PEP517 holdouts, there's little pressure upstream for them to port to a proper build system yet, as while setuptools deprecated the `setup.py` entrypoint some time ago, there's no removal in sight yet, so the only pressing side is on Gentoo's where we want to cleanup distutils-r1's support for that. It was arguably a mistake to really have these packages use distutils-r1 in the first place. The obvious workaround for now is to invoke setup.py manually w/ python-single-r1, and punt the question until setuptools removal of the entrypoint looks closer (at which time, other distros will be putting pressure on upstreams too). Of course, if at the time of such a setuptools change, the package is still not fixed, then we'd have to remove it. (The same issues apply to bug #922396 which isn't fixed by this, but hopefully won't be an actual problem until that aforementioned removal in setuptools itself of the other bits.) Bug: https://bugs.gentoo.org/922396 Closes: https://bugs.gentoo.org/909980 Closes: https://bugs.gentoo.org/923435 Closes: https://bugs.gentoo.org/952274 Signed-off-by: Sam James <sam@gentoo.org> dev-build/gyp/gyp-20200512145953-r1.ebuild | 67 ++++++++++++++++++++++++++++++ dev-build/gyp/gyp-99999999999999.ebuild | 48 +++++++++++++-------- 2 files changed, 98 insertions(+), 17 deletions(-)
